3 ms·
I don't really know what that comment was about. I've been using Postgres with a thoroughly-Unicode application stack (Django) for quite some time and never had
by ubernostrum 18y ago
I don't really know what that comment was about. I've been using Postgres with a thoroughly-Unicode application stack (Django) for quite some time and never had a problem...
- fauigerzigerk 18y agoWhich locale did you use to initialise your environment? It may well be that you haven't run into the LIKE + indexes issue or didn't notice it because the table didn't have a lot of data in it. By the way, do you realise that Django's ORM does not support optimistic locking in a transactionally safe way?
- ubernostrum 17y ago"It may well be that you haven't run into the LIKE + indexes issue or didn't notice it because the table didn't have a lot of data in it." I dunno, the backups (pgdump -> bzip), last time I looked at one, were over 6GB, so I'd say there's some data in there. I've just never seen Unicode-related issues. "By the way, do you realise that Django's ORM does not support optimistic locking in a transactionally safe way?" It doesn't really expose locking, period; consult the many threads on the dev list to find out why.