Re: A proposal to change psqlodbc

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: A proposal to change psqlodbc
Date: 2001-04-24 04:15:26
Message-ID: 3AE4FDDE.8D6D03E1@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Tom Lane wrote:
>
> Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
> > If there's no objection, I would change the current
> > source in a week or so.
>
> This seems like something to do during 7.2 development, not as part
> of post-7.1 bug fixing.
>

I can wait to commit it if the 7.2 branch is near
but have a basic question.

What does 7.2 development mean for clients(psqlodbc) ?
Certainly 7.2 would require some changes on clients
and I would request some features for psqlodbc.
But most changes in client libraries are/have been
independent from servers' changes. Strong binding to
servers' implementation is one of the most abominable
thing for clients. Psqlodbc driver has kept backward
compatibility and we have always been able to replace
the old driver by the latest one. As long as psqlodbc
doesn't intend a big change(e.g. ODBC level 3 support)
of its own, it doesn't seems to need the branch. Though
initdb is a critical restriction for servers, clients
are(should be) free from the restriction...

regards,
Hiroshi Inoue

P.S. The change would be a bug fix in a sense though
I'm not sure. Both the driver manager and each ODBC
driver have ODBC functions of the same name. ODBC
function calls inside a driver may call the functions
of the driver manager.

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Bruce Momjian 2001-04-24 04:44:51 Re: A proposal to change psqlodbc
Previous Message Tom Lane 2001-04-24 02:11:28 Re: A proposal to change psqlodbc