I do not like this. Should we put to a vote the default behavior of db(...).like(...)? the thing is whatever we do will behave differently than before on different databases.
On Wednesday, 3 September 2014 11:11:27 UTC-5, Anthony wrote: > > On Wednesday, September 3, 2014 9:37:24 AM UTC-4, Massimo Di Pierro wrote: >> >> Hello Joe, >> >> yes we made this change. The problem is that its previous behavior was >> undetermined and was different across databases. So we treated it like a >> bug. >> LIKE is supposed to be case sensitive so we made sure like(...) is also >> case sensitive consistently across supported databases (or so we think). >> You can change that behavior: >> >> like(..., case_sensitive=False) >> > I wonder if we should add an option to set that database-wide -- something > like DAL(..., case_sensitive_like=False). > > Also, should .startswith and .endswith have a case sensitive option? > > Anthony > > -- 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.
