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
mysql specific qquery #816
Comments
Can you provide a pointer to it? I don't see it in the 2.0 code when I search for it. |
Strange, I can't seem to find it in the 2.2.3 version. But in one of our projects I do have this piece of code. Which we actually use in production. I have no idea how we got this though...
|
This code is Mysql specific, and so either would not be in the core because of that, or was removed because of that. Perhaps it was a plugin? In any case, to be in core, it would need to be generalized a bit. Mysql, Oracle and Postgres all use different syntax to do regular expression matching, so this needs to be pushed down into the database adapters somehow. |
I looked a bit further and it looks like a colleage of mine added this part. So it might be inspired by a patch on the old qcubed trac website. |
Ah darn, that was indeed added by myself it seems. It's been a few years since I did that and my mistake was to not compare with the vanilla classes - apologies for the confusion! Lesson learned. |
It can be done as a plugin to the QQuery package when we factor it out from qcubed to something like |
Agreed. However, I think there is likely a database agnostic way to do REGEXP using database adapter calls. But, in general I agree that there is a place for a plugin, or even core extensions to the various databases. For example, |
Just noticed that apparently QQ::Regexp has been removed in the beta-3.0 branch.
What was the reason for that step and what is the recommended workaround if I used a few (mysql) queries using QQ::Regexp in a 2.x project?
The text was updated successfully, but these errors were encountered: