Repository navigation
Upstream: OpenSearch SQL ODBC follow-up fix PR #115 merged, verified on 20fc51d - #183
Merged
Merged
Conversation
…on a Linux build of 20fc51d Signed-off-by: singhpratech <42719720+singhpratech@users.noreply.github.com>
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
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.
Tracker and compatibility row updates for opensearch-project/sql-odbc#115 (the result-set
timestamptype-map entry), approved and merged by the maintainer on 2026-11-04 as 20fc51d.Verified on a Linux build of the merge commit against OpenSearch 3.9.0:
SELECT TIMESTAMP '2024-02-29 13:45:10'is described asSQL_TYPE_TIMESTAMP(93) and read as that instant, and a date-mapped index column reaches adbcBridge astimestamp[us]instead ofstring. Both halves of #101 are now fixed onmain; no release carries any of it yet.docs/compatibility.jsonregenerated from the edited row.