Fix database-specific example SQL#1298
Open
lovasoa wants to merge 2 commits into
Open
Conversation
lovasoa
force-pushed
the
fix-database-example-sql-dialects
branch
2 times, most recently
from
bbaeae1 to
c355cd2
Compare
lovasoa
force-pushed
the
fix-database-example-sql-dialects
branch
from
c355cd2 to
d9ab464
Compare
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.
This splits out dialect fixes that are useful independently from the SQLx driver migration PR.\n\nChanges:\n- Use MySQL CONCAT/backticks in MySQL-backed examples.\n- Use SQL Server OPENJSON and string conversion in the MSSQL survey example.\n- Add an MSSQL-specific CSV response fixture where string literal/concatenation syntax differs.\n\nValidation:\n- cargo fmt --all\n- cargo test data_formats::test_csv_body