-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More config-records are selected than it should #787
Conversation
The "%" in the LIKE-statement selects more config-records than it should. For example, if you have 2 themes "mytheme" and "mytheme-mobile" and lets say "mytheme" is the active one, this query selects all configs from both themes, because LIKE "mytheme%" also matches "mytheme-mobile". Whats the purpose of this "%" anyway?
Hey @JaroslavHerber,
What do you think about this? /Florian |
Hey @flow-control, thank you for your comment. Meanwhile I figured out, why the "%" is there. It's because of this const: .. which is used in init() to select and load all module-configs at once: I'll reconsider a better solution... Best regards, Jaro |
Hey @JaroslavHerber, we will run this branch through our internal CI and merge if everything is green. /Flo |
This should fix the problem. The "%" is moved to the only place, where it is needed ->line 405 What do you think?
Hey @JaroslavHerber, just an update for you: I rebased your pull request on latest /Flo |
Hello @JaroslavHerber, thank you very much, internal CI is also 💚, just merged everything. /Flo |
Hi @flow-control , thats awesome. Thank you very much :) Best regards, |
The "%" in the LIKE-statement selects more config-records than it should.
For example, if you have 2 themes "mytheme" and "mytheme-mobile" and lets say "mytheme" is the active one, this query selects all configs from both themes, because LIKE "mytheme%" also matches "mytheme-mobile".
Whats the purpose of this "%" anyway?