No apologies necessary: if anything, _I_ was the one getting a little
too gruff. In fact, _this_ time we did uncover a new aspect of this
problem: connection pooling can get in the way.
Ross
On Fri, Nov 16, 2001 at 09:56:03AM -0700, Jason Earl wrote:
>
> Thanks for being patient with me. I must have fallen on my head
> yesterday or something. I *knew* currval and nextval were backend
> specific. I got confused because I am working on a middleware layer
> with a connection pool that grabs a connection and holds it until the
> transaction is finished. Each new transaction might grab a different
> backend, but you won't get a new backend until your transaction is
> finished.
>
> In other words, in my application the easiest way to insure that
> currval and nextval work like they should is to start a transaction
> (which grabs a backend connection).
>
> Apparently this has led to some very fuzzy thinking on my part. My
> apologies for sending contradictory and confusing posts to the list,
> and thanks for clearing that up.
>
> Jason
