Hi,
Please advise.
We have a product with a PostgreSQLdatabase (UTF-8, PG 8.0 and 8.3)
It has a (legacy) client app that uses client_encoding = win1521 on the
connection since it uses win1252 internally.
The legacy app will be around for several years.
It cannot change to unicode.
There is a
Hi all,
We have a product with a PostgreSQLdatabase (unicode)
It has a (legacy) client app that uses client_encoding = win1521
The legacy app will be around for several years.
It cannot change to unicode.
There also is a new client app, written in java.
It uses client_encoding = unicode.
The p
Hi All,
please advise
I'm not getting my PostgreSQL 9.2 to return the correct lc_time
See psql output below.
lc_monetary and the lc's do work correctly
postgresql.conf is set to lc_time = 'nl_NL'
the output of locale -a includes nl_NL
[root@d01 ~]# psql db user
psql (9.2.1)
Type "help" for help
Thanks very much Tom and Adrian.
Solved. I will RTFM better next time.
Thanks again, Joek
Adrian Klaver schreef:
On 01/07/2013 07:56 AM, Tom Lane wrote:
Adrian Klaver writes:
On 01/07/2013 06:45 AM, J. Hondius wrote:
I'm not getting my PostgreSQL 9.2 to return the correct lc
I agree that there are better ways to do this.
But for me this works. (legacy driven situation)
INSERT INTO tbinitialisatie (col1, col2)
SELECT 'x', 'y'
FROM tbinitialisatie
WHERE not exists (select * from tbinitialisatie where col1 = 'x' and
col2 = 'y')
LIMIT 1
Pau Marc Muñoz Torre
