New parser for layer datasources - #7067
Open
laurentj wants to merge 3 commits into
Open
Conversation
laurentj
force-pushed
the
new-connexion-string-parser
branch
2 times, most recently
from
August 7, 2026 11:27
0dc32ce to
5b14a36
Compare
It has a better support of parameter values and quotes than a parser based on regexp.
Also better support with UTF-8 string, when values contains non-US characters.
We will be able to retrieve parameters already parsed.
laurentj
force-pushed
the
new-connexion-string-parser
branch
from
August 10, 2026 16:16
83b55b3 to
0d466dd
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.
Fix several potential issues when the connection strings contain special characters into parameters values.
It has a better support of parameter values and quotes than a parser based on regexp. Support of escaped quote in all values etc.
It is probably faster than the previous parser, as it doesn't have to execute a regexp for each parameters.
Funded by 3liz.