Repository navigation
test: cover DM data types and connection options - #6
Merged
Merged
Conversation
skhe
marked this pull request as ready for review
September 26, 2026 12:50
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.
Summary
TIMEbinding shifting five minutes under Asia/Shanghai historical timezone rules. Run the hosted real-DM suite withTZ=Asia/Shanghaito retain the regression signal.DECIMAL(30,8)write defect.Verification
go test ./..., actionlint, workflow YAML and version checks passed locally.Known gap
Binding
12345678901234567890.12345678toDECIMAL(30,8)stores a zero fractional part. This PR documents the failure; it is not safe to claim that high-precision decimal writes are covered. Timeout and app-name effectiveness also need dedicated checks.