From: | Pedro Doria Meunier <pdoria(at)netmadeira(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Posgresql to MSsql encoding problem |
Date: | 2009-10-09 14:49:49 |
Message-ID: | 4ACF4D8D.3000105@netmadeira.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Sam,
Thanks for your answer! :)
The matter of fact is that the script itself is the connected client
where the postgresql server is concerned.
It then connects to another server (the M$SQL one) and, on a row
basis, inserts data coming from the aforementioned connection...
So, to all effects, the script is *the* client... :)
Best regards,
Pedro Doria Meunier
On 10/09/2009 02:38 PM, Sam Mason wrote:
> On Fri, Oct 09, 2009 at 11:39:47AM +0100, Pedro Doria Meunier
> wrote:
>> I cannot simply use "Set Client Encoding to LATIN1" as the
>> "client" itself is the script ... :)
>
> What does this mean? surely if it's just a "script" you can put
> another line at the beginning of the script that says this?
>
> If you really can't do this, how about using ALTER USER to change
> the the user that they use latin1 by default?
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkrPTYQACgkQ2FH5GXCfxAvzSQCfV1tdIq3NSQVN0O8gNfQS1Iok
wxMAoIyGe2pQeWz4k3HSaeIEOaT4r49G
=/gqA
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2009-10-09 15:02:46 | Re: Posgresql to MSsql encoding problem |
Previous Message | Sam Mason | 2009-10-09 13:38:47 | Re: Posgresql to MSsql encoding problem |