On Tue, 1 Jul 2003, Stephan Szabo wrote: > > On Wed, 2 Jul 2003, Behdad Esfahbod wrote: > > > I'm new to the list, so don't flame at the first date ;). > > > > I usually use PostgreSQL for multiple languages, so I needed to > > set locale per connection, or can change the locale on the fly. > > I don't know if there is any such ability integrated in or not, > > so I have wrote my 10lines function as a wrapper around > > setlocale, that is attached. So what I do is just a simple > > "SELECT locale('LC_COLLATE', 'fa_IR');" at connection time. Let > > me know if there is any standard way already implemented. > > Hmm, I'd think there'd be some potential for danger there. I don't play > with the locale stuff, but if the collation changes and you've got indexed > text (varchar, char) fields, wouldn't the index no longer necessarily be > in the correct order?
I read in the FAQ that indexes for text fields is used just if default C locale is used during initdb, well, humm, is not the case on most distros. BTW, such a function is really needed to make Unicode collation algorithms effective. I may be able to convince my provider to define the function, but I can't convince him to start the backend with my desired locale! -- Behdad Esfahbod 11 Tir 1382, 2003 Jul 2 http://behdad.org/ [Finger for Geek Code] If you do a job too well, you'll get stuck with it. ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings