Release/2019.09 #38
Merged
Release/2019.09 #38
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
…nd SQL_LONGVARCHAR for BLOB and CLOB data type rather than SQL_C_DEFAULT. (CUBRID#10)
…should return SQL_WCHAR instead of SQL_WVARCHAR for the CHAR(n) database type under utf-8 charset. (CUBRID#11)
…ad, GET_MODULE_HANDLE_EX_FLAG_PIN flag was used when calling the GetModuleHandleEx function at DLL_PROCESS_ATTACH state in DllMain. (CUBRID#12)
* The SQLGetInfoW function conform to the following odbc specification. "If *InfoValuePtr is a Unicode string (when calling SQLGetInfoW), the BufferLength argument must be an even number; if not, SQLSTATE HY090 (Invalid string or buffer length) is returned." * The SQLGetInfoW function conform to the following odbc specification. "If InfoValuePtr is NULL, StringLengthPtr will still return the total number of bytes (excluding the null-termination character for character data) available to reurn in the buffer pointed to by InfoValuePtr." * The SQLGetInfoW function conform to the following odbc specification. "For character data, if the number of bytes available to return is greater than or equal to BufferLength, the information in *InfoValuePtr is truncated to BufferLength bytes minus the length of a null-termination character and is null-terminated by the driver." * The SQLGetInfo and SQLGetInfoW functions conform to the following odbc specification. "StringLengthPtr argument - Pointer to a buffer in which to return the total number of bytes (excluding the null-termination character for character data) available to return in *InfoValuePtr."
* [APIS-792] Providing the session information for current connection via DiagField * [APIS-792] Providing the session information for current connection via DiagField
* [APIS-796] Correct processing SQLCancel(...) * [APIS-796] revised: Correct processing SQLCancel(...)
…ID#23) * [APIS-795] Correct processing multi-bye binding in update query * [APIS-795] revised: Correct processing multi-bye binding in update query
* [APIS-797] Processing to get the query-plan for any queries. * [APIS-797] revised: Processing to get the query-plan for any queries.
…d I/O Definition (CUBRID#27)
…UBRID#28) * [APIS-799] Correct processing of string length for SUCCESS_WITH_INFO * [APIS-799] revised: Correct processing of string length for SUCCESS_WITH_INFO
…sa. (CUBRID#29) * [APIS-800] Correct processing for multi-byte to wide-char and vice-versa. * [APIS-800] revised: Correct processing for multi-byte to wide-char and vice-versa. * [APIS-800] revised: Correct processing for multi-byte to wide-char and vice-versa.
…D#31) * [APIS-802] Adding Test Case for ODBC update version * [APIS-802] Adding Test Case for ODBC update version (CPP Case) * [APIS-802] Adding Test Case for ODBC update version (conn-string utf-8 modify)
* [APIS-802] Adding Test Case for ODBC update version * [APIS-802] Adding Test Case for ODBC update version (CPP Case) * [APIS-802] Adding Test Case for ODBC update version (conn-string utf-8 modify) * [APIS-802] [Revised] Adding Test Case for ODBC update version (CPP Case)
* [APIS-802] Adding Test Case for ODBC update version * [APIS-802] Adding Test Case for ODBC update version (CPP Case) * [APIS-802] Adding Test Case for ODBC update version (conn-string utf-8 modify) * [APIS-802] [Revised] Adding Test Case for ODBC update version (CPP Case)
* [APIS-802] Adding Test Case for ODBC update version * [APIS-802] Adding Test Case for ODBC update version (CPP Case) * [APIS-802] Adding Test Case for ODBC update version (conn-string utf-8 modify) * [APIS-802] [Revised] Adding Test Case for ODBC update version (CPP Case) * [APIS-802] change connect (SQLConnto --> SQLDriverConnt) for user specify
beyondykk9
approved these changes
Oct 22, 2019
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.
ODBC 10.1.0.0002 Release
[APIS-788] Improve the functions of ODBC, patch the bugs related to multi-byte character set
[APIS-789] Upgrade build environment for Visual Studio
[APIS-790] Invalid BufferLength in SQLGetDiagRecW(...) for wide char
[APIS-791] SQLGetDiagRecW returns SQL State to S01000 for connection error.
[APIS-792] Providing the session information for current connection via DiagField
[APIS-793] Increasing default column length for derived column
[APIS-794] Processing multi-byte (utf-8) column name
[APIS-795] Correct processing multi-bye binding in update query
[APIS-796] Correct processing SQLCancel(...)
[APIS-797] Processing to get the query-plan for any queries.
[APIS-798] Correct processing multi-byte for native query (SQLNativeSql)
[APIS-799] Correct processing of string length for SUCCESS_WITH_INFO
[APIS-800] Correct processing for multi-byte to wide-char and vice-versa