> Should we put to a vote the default behavior of db(...).like(...)? The change to LIKE was to mirror the standard SQL and make it case-sensitive. Unfortunately, most web2py users expect LIKE to be insensitive.
There really should have been two commands from the beginning, LIKE and ILIKE (if we wished to copy Postgres keyword) My favorite solution is this: leave LIKE as it is (insensitive) and introduce SLIKE (sensitive). It would be a quirk of web2py, but once known easily remembered. We could leave our code unchanged, hurray!! Another more painful idea is to continue making LIKE case-sensitive, but then to introduce ILIKE so that everyone has the choice for each SQL statement. The problem is that we still have to change our code. The idea of using switches is much more horrible and really just a sticking plaster over the problem. IMO we should really have two explicit methods. -- 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.
