SQLGetData API call #14
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The setup API is meant to assist with installation of the driver.
stderr redirect will always work
- prompt_user_config() will pop up a dialog-box for connection config; - prompt_user_overwrite() will confirm with the user that a config is to be overwritten.
builds/.gitignore can get cleaned away, move its content into top .gitignore
- add a DSN to start from; - remove small code duplication in SQLDriverConnect; - change config priorities in ConfigDSN(), as follows (most relevant first): . 00-list received as parameter; . registry values; . defaults.
The values from the registry are read into a static buffer, indexed for each entry into the esodbc_dsn_attrs_st structure. Make sure that the indexing is done only for those values in the Registry that have a correspondence in the structure. Also, use SQLWCHAR explicitely instead of the TCHAR (should be same values for Unicode compilation, but might generate issues later.)
Moved from all-static/all-dynamic to all-static, to simplify code management.
- add a few more attributes to SQLGetInfo, some describing SQLGetData extentions - WIP on SQLGetData: set-up the temporary binding-unbinding on the requested column. Since SQLGetData requires no state maintenance except position in the source data, the binding is done with a static ARD; if the column index is lower-or-equal to a constant (128), the ARD will also use a static array of records; otherwise a new array is allocated-freed.
Also: - replace boolean conversion function, delegate that to the long long conversion function; - unify functions transfering SQLWCHAR and SQLCHAR strings to application to minimize code duplication; - build.bat : stop on error and propagate it to script exit; - CMakeLists.txt: add flag for parallel building.
move around the 0-terminator accounting, for better code clarity
Closed
droberts195
approved these changes
Aug 13, 2018
build.bat
Outdated
| :END | ||
| echo %ERRORLEVEL% | ||
| exit /b 0 | ||
| exit /b %ERRORLEVEL% |
There was a problem hiding this comment.
It looks like only one of these exits should be here
There was a problem hiding this comment.
Right, thanks, fixed.
.gitignore
Outdated
| @@ -1,3 +1,5 @@ | |||
| *.swp | |||
| driver/*.swp | |||
| builds/* | |||
There was a problem hiding this comment.
I think the canonical way to ignore a whole directory is just to list the directory name with a slash (no star). I.e. builds/.
This was referenced Aug 13, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the implementation for SQLGetData(). This function is an alternative to column binding: while SQLBindColumn() binds multiple subsequently have have all the bound buffers have data copied into with one SQLFetch() call, SQLGetData() will fetch one single column at a time. This functionality is used for "long data": in case the data source has a large amount of data in one (or multiple columns), it might not be feasible for the application to bind large enough buffers and have all the data in one go.
Theoretically the driver could access the cell data synchronously (or quasi~) with each SQLGetData call. In case of Elasticsearch/SQL however, this is not needed/possible, since each REST call will return an entire row.