in PostgreSQL equality ("X = Y") is case-sensitive

[wkornewald]

In the query dialog, string comparison is case-sensitive, so when you search for summaries containing "postgresql" you won't get results with "PostgreSQL", for example. For PostgreSQL it would be better to use the lower() function when doing exact matches and use case-insensitive altenatives where possible (e.g: ILIKE instead of LIKE).

[jonas]

Yes, it appears like the query module doesn't use the like() and like_escape() methods provided by the db connectin api.

[jonas]

r4435 fixes one bug where the "contains", "begins with", "ends with" query filters were case-sensitive on postgresql but insensitive on sqlite and mysql.

The "is" and "is not" operations however are still always case-sensitive. Should we change this behavior?

[cboos]

I think it's ok like that, as "is" suggests exact match.

[jonas]

Ok, then I'll resolve this ticket as fixed.

[Leandro Conde <leandor AT gmail>]

Replying to jonas:

Ok, then I'll resolve this ticket as fixed.

Could this solution be extended also to the session table sid string?