On 3 September 2014 12:45, Joe Barnhart <joe.barnh...@gmail.com> wrote:
I don't know whether it is possible in you case but a workaround maybe to the change the type of the fields searched in PostgreSQL to 'citext' which enables case insensitive indexing en searching in the backend. I have experimented with it and it did not break web2py. I did not even have to change my models. And I did not lose any data. Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3) -- 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.
