[
http://issues.apache.org/jira/browse/IBATISNET-104?page=comments#action_12360407
]
Ron Grabowski commented on IBATISNET-104:
-----------------------------------------
Clinton suggested we do something like this:
using (ISession session = new SqlMapSessionProxy(this.DataSource)
{
rows = statement.ExecuteUpdate(session, parameterObject);
}
and have the proxy intercept OpenConnection to actually open the connecction if
there is a cache miss. I think this is easier and more relieable than the Pre
and Post events and we shouldn't have to change other code in
CachingStatement.cs
> QueryForXXX do not check cache before opening/closing connection
> ----------------------------------------------------------------
>
> Key: IBATISNET-104
> URL: http://issues.apache.org/jira/browse/IBATISNET-104
> Project: iBatis for .NET
> Type: Wish
> Components: DataMapper
> Versions: DataMapper 1.2.1
> Reporter: H. E. Sum
> Priority: Minor
>
> I was confused by SqlMapper opening and closing database connections even
> when items were cached. I thought that it was fetching results from the
> database, but when I looked at the source, it seemed like the QueryForXXX
> methods are opening connections, calling MappedStatement to fetch results and
> then closing connections. Perhaps opening/closing should be pushed to the
> MappedStatement Class so connections are used only when there's a cache miss.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
