Fix JSON parameter tests for MySQL 8.0.40 key ordering changes #217
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.
MySQL 8.0.40 changed JSON behavior: keys are now sorted alphabetically on storage/retrieval, and JSON comparisons require explicit
CAST(@param AS json). MariaDB preserves original key order and doesn't require the cast.Changes
InsertJsonDocument()helperJsonMicrosoftDomQueryTest.Parameter_documentJsonMicrosoftDomQueryTest.Parameter_elementJsonNewtonsoftDomQueryTest.Parameter_elementExample
Tests now pass on both MySQL 8.0.40 and MariaDB 11.3.2+.
Original prompt
This section details on the original issue you should resolve
<issue_title>Assert.Equal() Failure: Strings differ</issue_title>
<issue_description>For MySQL 8.0.40 we have this error, but it works correctly for MariaDB 11.3.2 and upwards: