RLIKE, REGEXP

[Jim Musil]

I don't see support for RLIKE, NOT RLIKE, or REGEXP anywhere.

Is there support for this?

Jim

[jason kirtland]

Jim Musil wrote:
> I don't see support for RLIKE, NOT RLIKE, or REGEXP anywhere.
>
> Is there support for this?

Yes, you can use these operators and any others via the .op() method:

table.c.col1.op('rlike')('re')
not_(table.c.col1.op('rlike')('re'))
table.c.col1.op('regexp')('re')

-j

[Eric Lemoine]

As a a remark, ilike also is accessed in this way.

--
Eric

[Jim Musil]

Great! Thanks for pointing it out to me.

[iain duncan]

Is it possible to use them with the ORM too? Or am I misunderstanding
the above? If someone has the time to post an example of how one would
do an rlike version of

Resource.select_by( foo="bar" )

I'd love to see it.
Thanks
Iain

[Paul Johnston]

Hi,

>Resource.select_by( foo="bar" )
>
>
Untested, but I reckon this will work:

Resource.query.filter(Resource.foo.op('rlike')('bar'))

Paul

[Michael Bayer]

might need to call op() off the Table instance for now, might not
have added op() to the class-based properties....

[iain duncan]

Excuse what may be a stupid question, but is this for both 0.3 and 0.4
or just the new stuff? ( I know, I gotta upgrade soon now! )

Thanks
Iain

[Michael Bayer]

you can say query.filter(sometable.c.somecolumn.op('rlike')('bar'))
in any 0.3 or 0.4 version.