|
From: <tri...@tr...> - 2003-08-13 18:39:23
|
According to JDBC 3.0 a pooled connection should close any statements when the close method is called, and so should a non-pooled connection. A statement should close any resultsets when it is closed. I don't think JDBC 2.0 was that explicit, and there might be a few JDBC drivers that are not well behaved. I'll take a look at adding close statements for all resultsets and statements in addition to the connections. This should not harm current functionality. Thomas > > > Kopylenko, Dmitry wrote: > > >Would closing connection automatically take care of closing Statement and > >ResultSet? I guess it all depends on the JDBC driver. > > > > > well the thing is if it's a pooled connection, closing it doesn't really > do anything except > to return it to the pool. At least according to my naive understanding > of things. > But I might be wrong. > > Cheers > > Justinus > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |