Re: Persistent Sessions in DB connection for QZDASOINIT, implemented by Nathan

I think that in your application framework that *might* have been the case but the DBManager was "keyed" by role ID and pooled connection ID. I saw that kind of structure in AEE170. I can't remember the exact mechanism for retrieving the role as the user switched between applications but that info was stored in the userContainer which was a servlet session object.
Actually we should have gotten down to a role/fiscal year level of detail. Then it would have been easier to switch between fiscal years without having to change the role ID characteristics.

Hindsight is always 20/20....

Pete


Nathan Andelin wrote:

From: Pete Helgren
So this isn't really pooling at the user level... Many users
could be using the same "role" and thus using the same
pooled connection.

Hmmm. I thought that under the database maintenance model, DB connections were based on Session ID and Role ID. And that individual users could toggle between multiple roles within one session. I hope I didn't mislead anyone.

Oh well, at least is sounds like Richard, Aaron, and even Thorbjørn have in one case or another maintained database connections by individual session.

Nathan.