> I'm not sure the locale per database solution is a silver bullet.
> With this, still we cannot solve the issue, for example, a LATIN1
> encoded text includes several languages at a time, thus it needs
> multiple locales. Or we cannot have multiple different language
> columns, tables at a time because it requires multiple locales. Same
> thing can be said to Unicode too. After all it seems a half baked
> solution to me.
There is only one correct solution -> support of COLLATES. With
COLLATES you can choise locale per database, per table, per column,
per db operation. This is one point where PostgreSQL is late over
In response to
pgsql-hackers by date
|Next:||From: Simon Riggs||Date: 2007-10-05 12:25:01|
|Subject: Polymorphic arguments and composite types|
|Previous:||From: Simon Riggs||Date: 2007-10-05 10:58:42|
|Subject: EXPLAIN doesnt show Datum sorts explicitly|