|
|
|
|
|
by JelteF
3232 days ago
|
|
One of the main things I ran into when migrating from MySQL to postgres was that the default text columns (TEXT, VARCHAR, etc) behave differently when searching. MySQL matches text case insensitive, while postgres matches it case sensitive. This resulted in searches for content suddenly not returning data. Luckily there's an official CITEXT extension for postgres [1], which matches text case insensitive and adds the correct indices for doing so efficiently. [1] https://www.postgresql.org/docs/9.1/static/citext.html |
|
This is of course only when you set a case insensitive collation (_ci).
But I agree this can be a problem because case insensitive collations are used a lot in MySQL.
Also other collations can be a trouble. For example the collation that returns results for both 'ß' and 'ss' (German)