As a side note remapResult is a performance cost. It evaluates the bean to result mapping every time the statement is called.
Brandon On Wed, 05 Jan 2005 08:07:28 -0700, Larry Meadors <[EMAIL PROTECTED]> wrote: > I think that <select...remapResults="true"> will fix this (and yes, that is > new in 2.0.9). > > Larry > > >>> Peter Köhler (JIRA) <ibatis-dev@incubator.apache.org> 01/05/05 8:01 AM >>> > Oracle Schema switching and SQLMaps > ----------------------------------- > > Key: IBATIS-43 > URL: http://issues.apache.org/jira/browse/IBATIS-43 > Project: iBatis for Java > Type: Wish > Components: Documentation, SQL Maps > Versions: 2.0.9 > Reporter: Peter Köhler > Priority: Critical > > Hi to everyone at the iBatis team, > > i ran into a problem related to schema switching in oracle. > We have an application where you have a kind of single application / multiple > data (i.e. db-schemata). > We had "ORA-01007: variable not in select list" errors after switching the > schema. > The problem was that the two tables in our schemata were not absolutely > identical (one numeric column in one table was not deleted). > SQL Maps remembered the mapping of the table in schema1 when querying schema2. > This should be mentioned in the docs because it seems obvious that > select * from schema1.table behaves the same as > select * from schema2.table > when your application does not use the unnecessary column in schema2.table. > But it does not behave the same and produces a very nasty bug. > > Greetings from Frankfurt > > Peter Köhler > > P.S.: Did You change the behaviour in 2.0.9? > > -- > 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 > - > If you want more information on JIRA, or have a bug to report see: > http://www.atlassian.com/software/jira > >
