fix: namedValue namedDatevalue usage error #1575
Merged
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
Fixes #1555 query parameter binding for queries using named date values such as clickhouse.DateNamed(...).
Previously, if the query contained Named parameters (e.g., {table:Identifier}) and also used DateNamed, the driver returned ErrExpectedStringValueInNamedValueForQueryParameter.
This update extends bindQueryOrAppendParameters to support driver.NamedDateValue types and formats them using formatTimeWithScale, ensuring proper formatting and compatibility with the query parameter protocol.
Checklist