It appears that what was committed was a variation based on the original patch. Using the latest code from trunk QueryForObject<T> now calls to the database for every call regardless of prior caching. I have attached another patch that addresses this. Let me know if this is still not right. I was a bit curious on why the original changes were made from the first patch.
Thanks, Chris On 9/15/07, Gilles Bayon (JIRA) <[EMAIL PROTECTED]> wrote: > > > [ > https://issues.apache.org/jira/browse/IBATISNET-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] > > Gilles Bayon closed IBATISNET-242. > ---------------------------------- > > Resolution: Fixed > > In SVN > > > Cache error with QueryForObject<T> > > ----------------------------------- > > > > Key: IBATISNET-242 > > URL: https://issues.apache.org/jira/browse/IBATISNET-242 > > Project: iBatis for .NET > > Issue Type: Bug > > Components: DataMapper > > Affects Versions: DataMapper 1.6.1 > > Reporter: Gilles Bayon > > Assignee: Gilles Bayon > > Fix For: DataMapper 1.6.2 > > > > > > Reported by Kenneth Olsen and patch by Christopher DeGuise > > User _user = i.QueryForObject< User>( "stsGetOnEmail", email); > > When doing this, the error strikes: > > - I pass "1" as parameter in email, which will return NULL from db > > - I pass "1" again as parameter in email, which and the error pops up > with: Unable to cast object of type 'System.Object' to type 'Domain.User'. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
IBATISNET-242 (2nd).patch
Description: Binary data
