-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SNOW-710476: bulk update essential #776
base: master-2.0.0
Are you sure you want to change the base?
SNOW-710476: bulk update essential #776
Conversation
8236377
to
b8664ca
Compare
4aec3d8
to
10ecadb
Compare
@sfc-gh-jszczerbinski cc @sfc-gh-dprzybysz Please help me to check what's the failure on |
@sfc-gh-ext-simba-hx I see some problems related with CMake on jenkins:
@sfc-gh-jszczerbinski was changing the minimal version of make recently - I think we should merge or rebase the 2.0 branch with main |
0a61e80
to
7dcf893
Compare
3540460
to
ca93ea8
Compare
Hi @sfc-gh-ext-simba-hx now all linux aarch64 test jobs fails with:
|
{ | ||
namespace Client | ||
{ | ||
ClientBindUploader::ClientBindUploader(SF_STMT *sfstmt, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ClientBindUploader is separated from BindUploader since BindUploader is fully ported from ODBC and will be still used in ODBC?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BindUploader is ported from ODBC and refactored so it can be reused on both libsfclient and ODBC side. When reusing it on ODBC side there would be ODBCBindUploader class to have ODBC specific implementation.
namespace Client | ||
{ | ||
|
||
class BindUploader |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
with add this file to include/snowflake for ODBC usage? if so we should consider it not as a public API of the driver - could we put some "internal" notice on top of this header file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and for 2.x we can mark in that way all files that we should consider internal
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure. Will add "internal" notice on top of the header file.
I think we might need that in most (if not all) hpp files since in general libsfclient is C API library any C++ implementation should be for internal use only.
@@ -875,6 +906,8 @@ uint64 STDCALL snowflake_num_params(SF_STMT *sfstmt); | |||
* | |||
* For Positional parameters: | |||
* SF_BIND_INPUT name = NULL; | |||
* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpicking: seems to be unnecessary new lines?
essential functionality only.
Will add following features in separated PR: