3 ms·
We are currently using MS SQL Server, but have looked at the possibility of using Postgres in the future. One major stopping point for us is the fact that on S
by a_m0d 13y ago
We are currently using MS SQL Server, but have looked at the possibility of using Postgres in the future.
One major stopping point for us is the fact that on SQL Server we use a Case Insensitive, Accent Insensitive collation. Postgres doesn't support this, and apparently has no plans to.
We have many stored procedures in TSQL which are built around the assumption of CI,AI. Converting these will be a lot of work, but the lack of CI,AI collation would be by far the biggest pain point.
- lneves 13y agoSee the docs for: citext: http://www.postgresql.org/docs/9.2/static/citext.html http://www.postgresql.org/docs/9.2/static/citext.html unaccent: http://www.postgresql.org/docs/9.2/static/unaccent.html http://www.postgresql.org/docs/9.2/static/unaccent.html I think you can make it work.