Fix duckdb & sqlite character_length scalar unparsing #13428
+133
−12
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.
Which issue does this PR close?
N/A
Rationale for this change
When unparsing
CharacterLengthFunc
scalar function to DuckDB & SQLite syntax SQL query, theCharacterLengthFunc
scalar function need to be unparsed tolength
, sincelength
is the equivalence ofCharacterLengthFunc
in DuckDB & SQLite.DuckDB length()
SQLite length()
What changes are included in this PR?
DuckDBDialect
, which implements theDialect
traitcharacter_length_style
forDialect
trait for determining theCharacterLengthStyle
to use for a dialectcharacter_length_to_sql
, which unparses theCharacterLengthFunc
tolength
orcharacter_length
based onCharacterLengthStyle
Are these changes tested?
Yes
Are there any user-facing changes?
No