| From: | "Anoop Kumar" <anoopk(at)pervasive-postgres(dot)com> |
|---|---|
| To: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>, "Hiroshi Saito" <saito(at)inetrt(dot)skcapi(dot)co(dot)jp>, <pgsql-odbc(at)postgresql(dot)org> |
| Cc: | "Marko Ristola" <Marko(dot)Ristola(at)kolumbus(dot)fi>, "Johann Zuschlag" <zuschlag2(at)online(dot)de> |
| Subject: | Re: Continuing encoding fun.... |
| Date: | 2005-09-06 08:53:16 |
| Message-ID: | B4AF8C04F762D246A1E38EC5DFAEFC0B0379DC@blrmail2.aus.pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
> Done. Once you've removed the socket code, a new release seems in
order.
> Sound OK to you?
OK for me. A new release would be proper.
> It seems to me that the current case is correct - in the Unicode
driver
> we *must* run with client_encoding = 'UNICODE' or it won't work
> properly. That said, I wonder if we shouldn't just remove the if()
> altogether, and unconditionally set the client encoding for the
Unicode
> driver.
>
> Don't forget, this won't affect the ANSI/Multibyte case because it's
> inside a "#ifdef UNICODE_SUPPORT".
>
> What do you think Anoop?
>
As this is already inside "#ifdef UNICODE_SUPPORT", I don't find the
necessity for checking it again.
Regards
Anoop
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Saito | 2005-09-06 09:01:31 | Re: savepoint |
| Previous Message | Dave Page | 2005-09-06 08:02:54 | Re: Continuing encoding fun.... |