Re: ODBC Connection Pooling (Windows 2000 MDAC 2.7 patched, pgodbc-7.02.00.05)

From: Chris Gamache <cgg007(at)yahoo(dot)com>
To: pgsql-odbc(at)postgresql(dot)org
Cc: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Subject: Re: ODBC Connection Pooling (Windows 2000 MDAC 2.7 patched, pgodbc-7.02.00.05)
Date: 2003-09-05 16:13:48
Message-ID: 20030905161348.25810.qmail@web13802.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Rats... In that case, the application creating the connection would have to
issue a command to the back-end before running any other SQL statements.

--- Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> wrote:
> Chris Gamache wrote:
> >
> > That is my point exactly. That is why (windows?) connection
> > pooling breaks this model. It wouldn't be a problem if there
> > were a way to undefine currval() for all sequences...
> > It would be a command issued by the ODBC driver when the
> > connection is made (best), or by the connecting process as
> > its first order of business (do-able).
>
> How could the driver know if the connection is recycled ?
> SQL..Connect API function isn't called when the connection
> is recycled.
>
> regards,
> Hiroshi Inoue
> http://www.geocities.jp/inocchichichi/psqlodbc/

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message Lord Corwin 2003-09-05 19:21:59 Question: ODBC connection across 2 disimilar NT Domains
Previous Message Brian J. Erickson 2003-09-05 15:42:59 Re: ODBC, SQLExecute and HY010