docs: SingleStore catalogue NULL fix merged upstream (#47) - #145
Merged
Merged
Conversation
Approved and merged 2026-09-23 by the maintainer, merge commit e760503629, closing memsql/singlestore-odbc-connector#46 the same minute with no changes requested. That completes the pair reported on 2026-09-04: both defects are now fixed by our pull requests. Not in a release yet; master is at 1.2.2 with no version bump staged, so the shipped-in line waits for the next tag.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The second of the two SingleStore fixes merged: #47, 2026-09-23T14:52:44Z, merge commit
e760503629, closing #46 the same minute. Approved with no changes requested.On a connection opened without
Database=,TABLE_CATfell back to the client library's current-database field, which stays NULL after aUSE, soSQLColumnsandSQLPrimaryKeysreachedstrdup(NULL)and took the client process down. The fix answers NULL forTABLE_CATinstead, with a test intest/catalog2.cfor that connection shape.That completes the pair reported on 2026-09-04 — both defects fixed by our pull requests, both merged the same day. #48's row moved in #142; this is #47's.
No compatibility-note change is needed: the crash was never recorded as a matrix caveat, because the entry supplies
Database=and so never hit it.Still unreleased —
masteris at 1.2.2 with no version bump staged, so the shipped-in line waits for the tag.