point-cut for that method,
inside advice code process the connection, set db side settings,
-Original Message-
From: Steven Pannell [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 05, 2006 10:15 AM
To: 'user-java@ibatis.apache.org'
Subject: RE: make DB call for every new conne
L PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 04 January 2006 17:12
To: user-java@ibatis.apache.org
Subject: Re: make DB call for every new connection
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Out of pure curiosity why would you do something like this. What
does it buy you?
Nathan
On Jan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Out of pure curiosity why would you do something like this. What
does it buy you?
Nathan
On Jan 4, 2006, at 6:59 AM, Steven Pannell wrote:
Hi,
I want to set some session infomation for a connection I make using
ibatis
on my oracle database
This isn't an iBATIS problem so much as it is a connection pooling
problem. That is, you'd have the same problem with almost any
connection pooling solution (unless you were planning on holding
connections open forever).
So the best way to deal with this is to tackle the problem at the
source.
Hi,
I want to set some session infomation for a connection I make using ibatis
on my oracle database. This works fine as follows:
client.queryForObject("setClientInfo",null);
executes a stored procedure and sets my session data. But there is a
problem. ibatis allows for multiple connections t
