On Thu, Mar 16, 2006 at 09:21:56PM -0500, Greg Stark wrote:
> In any case having actually implemented multilingual sites I can't imagine one
> locale per table being useful at all. You always end up wanting per column,
> even per array element locales.
Exactly, in the SQL standard it's referred to
"Tomi NA" <[EMAIL PROTECTED]> writes:
> Here's an idea: let's make the locale a table-level setting, settable at
> table creation time so that it's concievable to use postgresql to build,
> say, a turist information site supporting english, german, spanish and
> italian at the same time.
Which l
On 3/16/06, Harald Armin Massa <[EMAIL PROTECTED]> wrote:
on bugs Magnus wrote:> It's a matter of picking the correct locale when you initdb your database.and he is PERFECTLY right. Getting the locale wrong while doing intidb can really screw up ones day.
But: because of initdb being at the very
