On Friday 9. October 2009, Scott Marlowe wrote:
>On Fri, Oct 9, 2009 at 8:49 AM, Pedro Doria Meunier
>
> 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 pos
On Fri, Oct 9, 2009 at 8:49 AM, Pedro Doria Meunier
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
-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 afo
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 y
On Fri, Oct 9, 2009 at 6:39 AM, Pedro Doria Meunier
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi All,
>
> I have this PHP script that simply dumps (inserts) data from a
> Postgresql server to a customer's M$SQL server.
>
> The database in the PGSQL server is UTF-8 encoded where
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
I have this PHP script that simply dumps (inserts) data from a
Postgresql server to a customer's M$SQL server.
The database in the PGSQL server is UTF-8 encoded where the M$SQL
database uses LATIN1.
Accents, as expected, turn to gibberish...
