Workaround sqlite 3.53.0 regression on sqlite3_mprintf()#4745
Merged
rouault merged 1 commit intoOSGeo:masterfrom Apr 10, 2026
Merged
Workaround sqlite 3.53.0 regression on sqlite3_mprintf()#4745rouault merged 1 commit intoOSGeo:masterfrom
rouault merged 1 commit intoOSGeo:masterfrom
Conversation
rouault
added
funded through GSP
See https://sqlite.org/forum/forumpost/e2421578f4 Breaks the factory.objectInsertion unit test, or more generally if using getInsertStatementsFor() with a geodetic datum with an anchor epoch. Which shouldn't affect that many people
rouault
force-pushed
the
sqlite_3_53_0_workaround
branch
from
62d6c8d to
2f67ec9
Compare
jjimenezshaw
approved these changes
Apr 10, 2026
This was referenced Apr 10, 2026
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
2 participants
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.
See https://sqlite.org/forum/forumpost/e2421578f4
Breaks the factory.objectInsertion unit test, or more generally if using getInsertStatementsFor() with a geodetic datum with an anchor epoch. Which shouldn't affect that many people