I feel like the only clean approach is to have a LIKE and a ILIKE. The problem is that we don't have any mechanism to make compatibility breaking changes.
I think ideally applications should report what version of web2py or of the DAL they were made for (and if they don't, we assume they're older than 2.9.6 or something). That way we could have a PostgresPre296Adapter that had the old LIKE implementation and we would use that for the older applications. I'm all for maintaining backwards compatibility, I think it is absolutely indispensable, but we need a sane way to move forward while keeping it. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
