> >>> At this point in time, "no locale" is probably close to best
> >>> practice,
> >>> but it leaves you a lot of work.
> >> It does?
> > Well, there are just a lot of things that you want to be sort of
> > automatic that you end up having to do by hand.
> Such as? It's not a rhetorical question; I honestly don't know. For me,
> C locale simply solved my problem.
I would expect to run into problems with collation. In that case, you
may end up setting up separate databases for each language, as I
mentioned before in the mail that I forgot to post to the list so people
could correct me if I'm wrong.
Other than that, it depends on what functions the database will have.
If what is being done with the CJKT is pretty basic stuff, I may be just
another too-pessimistic voice.
In response to
pgsql-general by date
|Next:||From: Jon Lapham||Date: 2004-08-27 12:28:36|
|Subject: Re: performance of IN (subquery)|
|Previous:||From: David Wheeler||Date: 2004-08-27 11:54:29|
|Subject: Re: UTF-8 and LIKE vs =|