| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | rohtodeveloper <rohtodeveloper(at)outlook(dot)com> |
| Cc: | "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | Re: This may be a bug: odbc's function"check_client_encoding" have the same name with postgres's function. |
| Date: | 2014-10-28 23:37:28 |
| Message-ID: | CAB7nPqR9agJ9hV3CRZKtzwiXcBZcC1hNVoUFBnWWGjiB4bUTcw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
On Wed, Oct 29, 2014 at 2:35 AM, rohtodeveloper <rohtodeveloper(at)outlook(dot)com>
wrote:
> Well ,in fact, if I use the extension called odbc_fdw , the same problem
> will happen.
>
That's because the odbc_fdw will also call the odbc driver.
> The follow pictures explain the situation.
>
Ah, right, I completely forgot this fdw. Yeah it may be worth renaming that
in the odbc driver... Inoue-san, Saito-san, Heikki, thoughts about the
simple patch attached? check_client_encoding is used to extract an encoding
name from the connection settings. Perhaps we could do better than that.
--
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| 20141029_pgodbc_rename_check_encoding.patch | text/x-patch | 2.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-10-29 00:00:51 | Re: This may be a bug: odbc's function"check_client_encoding" have the same name with postgres's function. |
| Previous Message | blakeduffey . | 2014-10-28 20:58:02 | pgsql-odbc and client certs |