| From: | "Leif B(dot) Kristensen" <leif(at)solumslekt(dot)org> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Posgresql to MSsql encoding problem |
| Date: | 2009-10-09 15:11:07 |
| Message-ID: | 200910091711.07755.leif@solumslekt.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Friday 9. October 2009, Scott Marlowe wrote:
>On Fri, Oct 9, 2009 at 8:49 AM, Pedro Doria Meunier
>
><pdoria(at)netmadeira(dot)com> wrote:
>> -----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... :)
>
>It's a php script, right? Just issue a pg_query("set client encoding
>yadayada;") at the beginning.
PHP even has a special function for it:
pg_set_client_encoding($db, LATIN1);
--
Leif Biberg Kristensen | Registered Linux User #338009
Me And My Database: http://solumslekt.org/blog/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2009-10-09 15:15:53 | Re: interface for "non-SQL people" |
| Previous Message | Scott Marlowe | 2009-10-09 15:02:46 | Re: Posgresql to MSsql encoding problem |