-
Notifications
You must be signed in to change notification settings - Fork 428
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
Changes in preparation for 6.5.1 preview release #670
Conversation
Retry logic
To help debug an irreproducable/random mismatch error if it occurs in the future.
…#666) * Dont throw exception for colmetadata token * Adding a comment * Update comment * Adding a warning message * remove ignoreLengthPrefixedToken
* Added more information to error messages To help debug an irreproducable/random mismatch error if it occurs in the future. * Revert "Added information to error message" This reverts commit 25301e6. * Fix for microsoft#659 Added error handling logic for special cases. * Read message length Read the message length instead of reading until terminating character * Unsigned byte update Message length is an unsigned byte, converting before using. * Removed clunky hex conversions convert the byte straight to an int and use existing constants instead of making new ones * Narrowed trigger conditions fixed an issue where column names who had the hex token 'AA' would cause an error to be thrown. * Spacing fixes * Added test case * spacing adjustment * Edited test drop procedures Changed IF EXISTS DROP commands to be compatible with sql server 2008 * github spacing misalignment fixes * Changed test condition now only runs on compatible database or higher * Removed error check Removed a previous implementation in favor of one that changes the TDS parser * tdsreader change * removing test for now * enabled tests * github spacing fix * removed array import * removed "arrays" instead of "array" * spacing changes
Implement a more generic and compatible test in the future
Used in removed test
Codecov Report
@@ Coverage Diff @@
## dev #670 +/- ##
============================================
- Coverage 48.18% 48.16% -0.02%
- Complexity 2575 2577 +2
============================================
Files 113 113
Lines 26587 26587
Branches 4436 4436
============================================
- Hits 12810 12806 -4
- Misses 11645 11653 +8
+ Partials 2132 2128 -4
Continue to review full report at Codecov.
|
CHANGELOG.md
Outdated
- Test cases for Date, Time, and Datetime2 data types. [#558](https://github.com/Microsoft/mssql-jdbc/pull/558) | ||
|
||
### Fixed Issues | ||
- Fixed an issue where column type was not being returned correctly for spatial data types [#657](https://github.com/Microsoft/mssql-jdbc/pull/657) |
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.
"Fixed an issue where ResultSetMetadata returned incorrect columnType for Geometry and Geography data types."
CHANGELOG.md
Outdated
|
||
### Fixed Issues | ||
- Fixed an issue where column type was not being returned correctly for spatial data types [#657](https://github.com/Microsoft/mssql-jdbc/pull/657) | ||
- Fixed unnecessarily creating 2 connections when multiSubnetFailover is true [#662](https://github.com/Microsoft/mssql-jdbc/pull/662) |
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.
"Fixed server side CPU Affinity problems caused by uneven connection distribution across NUMA Nodes when multiSubnetFailover is true"
CHANGELOG.md
Outdated
### Fixed Issues | ||
- Fixed an issue where column type was not being returned correctly for spatial data types [#657](https://github.com/Microsoft/mssql-jdbc/pull/657) | ||
- Fixed unnecessarily creating 2 connections when multiSubnetFailover is true [#662](https://github.com/Microsoft/mssql-jdbc/pull/662) | ||
- Fixed an issue where TDS Packets weren't being completely parsed after reading rows [#664](https://github.com/Microsoft/mssql-jdbc/pull/664) |
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.
"Fixed an issue where Driver wasn't parsing TDS Packets completely to capture exceptions raised inside executed stored procedures"
CHANGELOG.md
Outdated
- Fixed an issue where setMaxRows() would throw an exception if showplan_text is on [#666](https://github.com/Microsoft/mssql-jdbc/pull/666) | ||
|
||
### Changed | ||
- Removed unused imports which force users to import the ADAL4J library [#652](https://github.com/Microsoft/mssql-jdbc/pull/652) |
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.
*forced
CHANGELOG.md
Outdated
- Fixed an issue where column type was not being returned correctly for spatial data types [#657](https://github.com/Microsoft/mssql-jdbc/pull/657) | ||
- Fixed unnecessarily creating 2 connections when multiSubnetFailover is true [#662](https://github.com/Microsoft/mssql-jdbc/pull/662) | ||
- Fixed an issue where TDS Packets weren't being completely parsed after reading rows [#664](https://github.com/Microsoft/mssql-jdbc/pull/664) | ||
- Fixed an issue where setMaxRows() would throw an exception if showplan_text is on [#666](https://github.com/Microsoft/mssql-jdbc/pull/666) |
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.
The issue isn't really exception from setMaxRows..
It should rather be: "Fixed an issue where driver throws exception when using setMaxRows() followed by query execution when SHOWPLAN_TEXT is ON"
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.
Not really. Driver was throwing an exception on setMaxRows().
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.
Let's still change it, as the internal call of setMaxRows (that throws exception) is done when client calls executeQuery(). So to the client app, its exception from query execution.
Updates to POM, README, CHANGELOG, and Driver version.