Skip site navigation (1) Skip section navigation (2)

Connection Pooling and currval

From: Chris Gamache <cgg007(at)yahoo(dot)com>
To: pgsql-odbc(at)postgresql(dot)org
Subject: Connection Pooling and currval
Date: 2003-02-25 20:12:15
Message-ID: 20030225201215.50956.qmail@web13805.mail.yahoo.com (view raw or flat)
Thread:
Lists: pgsql-odbc
I've just enabled Connection Pooling on the PostgreSQL+ (Beta) 7.02.00.05, and
I think I'm having some state problems. 

I think currval() is returning a value from a recycled connection where it
should be undefined.

I can not duplicate this problem because I can not get the timing right, but it
is indicitive of ODBC pulling an active connection from the connection pool,
and PostgreSQL thinking it is the same connection as before... I'm using a
DSN-less connection... Can I modify this string to ensure that stateful
variables are reset even though the connection has not been (really) severed?

Here's my connection string

"Provider=MSDASQL.1;Password=xxxxxxx;Persist Security Info=True;User
ID=xxxxxxx;Mode=ReadWrite;Extended Properties=""DRIVER={PostgreSQL+
(Beta)};DATABASE=xxxxxxx;SERVER=10.10.0.1;PORT=5432;UID=xxxxxxx;PWD=xxxxxxx;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=1;SHOWOIDCOLUMN=1;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTINGS="""

Any other suggestions?

CG


__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/

Responses

pgsql-odbc by date

Next:From: Ben TrewernDate: 2003-02-26 13:38:27
Subject: Re: Driver PostgreSql x dbExpress
Previous:From: 曾军Date: 2003-02-25 02:30:41
Subject: Transaction is affected by a recordset

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group