Re: This may be a bug: odbc's function"check_client_encoding" have the same name with postgres's function.

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: developer rohto <rohtodeveloper(at)outlook(dot)com>
Cc: "Inoue, Hiroshi" <inoue(at)tpf(dot)co(dot)jp>, PostgreSQL mailing lists <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-11-03 06:52:06
Message-ID: CAB7nPqRt_zQNbXQVCkVK66m_e_MdCK3VaRoh3itG_8suMO7vbw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

On Mon, Nov 3, 2014 at 3:26 PM, developer rohto <rohtodeveloper(at)outlook(dot)com>
wrote:

> Thanks very much.
> We decide to use your
> solution1(20141029_pgodbc_rename_check_encoding.patch).
> On the other hand, by the way, which solution does the community prefer to
> choose?
>
The potential solution by Inoue-san to reduce dependencies between library
objects is better.
--
Michael

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Heikki Linnakangas 2014-11-03 17:22:49 Let's use libpq for everything
Previous Message developer rohto 2014-11-03 06:26:14 回复： Re: This may be a bug: odbc's function"check_client_encoding" have the same name with postgres's function.