André R.
André R.
@enjoy-binbin Something to consider for 7.2 or 7.2+1? Would greatly benefit/simplify use and latency on bulk cache saving work against cluster.
> let me know if this can be removed: hmm, why do you think this should be removed? Or did we already discussed that somewhere?
@adamwojs / @alongosz POV?
So this will inject variables for all content views then, kind of like a default set of params each and every override rule can overload? Will it be siteaccess aware?
Regarding this PR I'm unsure, it seems to add a feature not available on the SQL engine, so better would be to make something that can work across both for...
Ok, we (@alongosz, ..) will try to investigate that with integration tests on API to better define this, thanks for finding this.
@alongosz We'll need to check from API perspective what we want to do with this one, for instance if we want to limit use to % to LIKE across engines...
Sounds like a core feature, something we should prioritize now. But if in core I would maybe not tie them to much to the internal settings structure of repo code,...
hmm, but do we want the lock in _our_ repo? Atm we don't keep locks in product repos, but when making tags we swap this so projects do keep them:...
Reminds me that we should consider adding .gitattribute for certain things also: https://medium.com/@pablorsk/be-a-git-ninja-the-gitattributes-file-e58c07c9e915 but that goes for more then just master