ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Koka Kiknadze" <226...@gmail.com>
Subject Re: Problem with SCOPE_IDENTITY() with SQL Server 2005 Express
Date Sat, 28 Apr 2007 22:36:51 GMT
Well seems all required modifications are in ConnectionLogProxy class. There
are four log statements starting with:

log.debug("{conn-" + id + "}...

Those should be changed to

log.debug("{conn-" + connection.hashCode()+ "}...

OR (just to keep the old autoincremnt ID-s too) to something like

log.debug("{conn-" + id + "; Hash= " + connection.hashCode() +"}...


On 4/25/07, Jeff Butler <jeffgbutler@gmail.com> wrote:
>
> Koka - If you have a patch to contribute, I'd be happy to look at it.
>
> Jeff Butler
>
>
>
> On 4/25/07, Koka Kiknadze <226057@gmail.com> wrote:
> >
> > Jeff, I've complained about it earlier, now seems you too find it
> > inconvenient that iBatis log shows
> >
> > [main] DEBUG com.ibatis.common.jdbc.SimpleDataSource - Returned
> > connection 18751079 to pool
> >
> > where 18751079  seems to be hash code of the connection, and on the
> > other hand it says
> >
> > [main] DEBUG java.sql.Connection - {conn-100003} Preparing Statement:
> >
> > and 100003 is just some autoincrement. It would be much more convenient
> > to have same hashcode 18751079 in place of 100003.
> >
> > Sorry for kind of OT.
> >
> >
> >
>

Mime
View raw message