soapbox = True Version 2.9.6 does indeed make LIKE case-sensitive -- at least for Postgres and perhaps other databases. The change is that case sensitivity now mimics the underlying database that you are using at the moment. So if you're a MySql user you'll probably keep case-insensitive as your default, but if you are a Postgres user, all of your searches just changed from case insensitive to case sensitive. And if you want to switch from one to the other, God help you.
Right off the bat, this killed my existing website. I do a lot of searches on strings (which is the whole point of using a database), and they are all case-insensitive. In fact, I never even knew the default in Postgres was case sensitive until this version of web2py. Until now, web2py protected me by providing a uniform DAL that made the underlying databases all look the same in this regard. I'm also miffed at this decision as I don't see an easy way to overcome it except by combing through the code and adding case_insensitive=True to every "like", "startswith", "endswith", etc. I know very smart people were involved in this decision and I respect their combined brainpower, esp. Niphlod who I think rules the earth on Python and DB knowledge. But there is a disconnect between the devs and users who just need to keep sites running without re-writing code because of an "upgrade". And I believe it weakens the DAL by exposing the underlying default of the database engine. It doesn't help us change from one DB engine to another, which is the biggest purpose of the DAL. soapbox = False -- 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.
