-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thank you Sam for the valuable input!
Best regards,
Pedro Doria Meunier
GSM: +351 96 17 20 188
Skype: pdoriam
Sam Mason wrote:
> On Sat, Apr 11, 2009 at 02:47:53AM +0100, Pedro Doria Meunier wrote:
>> Actually what I have is a fully internationa
On Sat, Apr 11, 2009 at 02:47:53AM +0100, Pedro Doria Meunier wrote:
> Actually what I have is a fully internationalized site by means of
> getttext.
> *Some* of the content comes from the PGSQL database where 2 tables
> relation with others (namely for sensor data description).
Why not continue u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Justin,
First of all thank you for your input. :)
Actually what I have is a fully internationalized site by means of
getttext.
*Some* of the content comes from the PGSQL database where 2 tables
relation with others (namely for sensor data descript
Pedro Doria Meunier wrote:
Hi all,
I'm wondering how to internationalize contents of a table, short of
having a column for each language string ...
Anyone with some experience to share? :)
Regards,
Pedro Doria Meunier
How about parent child table layout. The child table has one record for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'm wondering how to internationalize contents of a table, short of
having a column for each language string ...
Anyone with some experience to share? :)
Regards,
Pedro Doria Meunier
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Li
Tom Lane wrote:
Dennis Gearon <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
The indexes on the shared system tables (eg, pg_database) are the only
issue here. One possible solution is to require that no locale-aware
datatypes ever be used in these indexes. I think right now this is true
because "na
Dennis Gearon <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> The indexes on the shared system tables (eg, pg_database) are the only
>> issue here. One possible solution is to require that no locale-aware
>> datatypes ever be used in these indexes. I think right now this is true
>> because "name
Dennis Gearon <[EMAIL PROTECTED]> writes:
> Is there anyway for a single statement to access more than one database?
> Could a query, regexes, etc be facing indexes in different
> encodings/sorting collations if different databases in a cluster had
> different encodings/collations?
The indexes o
