arch 01, 2007 4:33 PM
To: user-java@ibatis.apache.org
Subject: RE: Simple question...
Hi,
I'm leaning towards the "no-way-in-the-world-would-this-work
configuration" :) I think you should specify only one transactionManager
element and include all SqlMaps from there. See the develope
al Message-
From: Niels Beekman [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 01, 2007 4:33 PM
To: user-java@ibatis.apache.org
Subject: RE: Simple question...
Hi,
I'm leaning towards the "no-way-in-the-world-would-this-work
configuration" :) I think you should specify only one trans
Hi,
I'm leaning towards the "no-way-in-the-world-would-this-work
configuration" :) I think you should specify only one transactionManager
element and include all SqlMaps from there. See the developers guide
(from the website) for some samples.
Niels
-Original Message-
From: Dave Rodenbau
Rowhandler example is in the dev guide. But seems I've found a way to do without it. > at this point changing the db schema is not an optionThe idea is to mimick splitting users tableMake a view like this
select userID, customproperty1 from usersTable where customproperty1 is not nullUNION ALLsele
Thanks Koka - But unfortunately at this point changing the db schema is not an option, i know i can add all those getter\setters but i was hoping to find a easier way. Can you point me to an example of custom row handler?- Original Message From: Koka Kiknadze <[EMAIL PROTECTED]>To: user-ja
Seems the only way would be to write custom rowhanlder.However, I'd change design of database to match java object, i.e. would have separated CUSTOMPROPERTY-ies into a separate table. In that case you'd be able to populate the list along the lines described in dev guide.
On the other hand iIf you t
