@Joe, let me go back and look at my correspondence about this... we may revert this change.
On Friday, 5 September 2014 05:34:11 UTC-5, Joe Barnhart wrote: > > I'm really unclear on this discussion. > > I use postgres (pg) and sqlite a lot. When using web2py on both of them, > I was doing case-INsensitive "like" comparisons by default. Yet the > underlying DB systems have opposite native defaults -- pg defaults to > case-sensitive and sqlite defaults to case-insensitive. > > From my limited perspective, it only appears that web2py switched from > mapping everything from case-insensitive to case-sensitive. It seemed > consistent across the database platforms I used before, and I assume it is > consistent now. Just reversed. > > Were there some databases which were not forced by web2py? Is that why > the devs changed it? If there is some deep underlying flaw in the previous > release of web2py, please tell me so I can feel better about this! > > -- Joe > > > On Thursday, September 4, 2014 11:05:39 PM UTC-7, Massimo Di Pierro wrote: >> >> 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. >> >> > -- 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.
