ah... thanks for the info ... but why would it have worked at all before? It only seems to have choked on mapping the CLOB. I assume this has to do with the mysteries of the driver, but i'd love to know...
Jeff Butler-2 wrote: > > Thisis the URL for the type 4 driver: > > jdbc:db2://localhost:50000/devdb > > This is the URL for the type 2 driver: > > jdbc:db2:DEVDB > > I assume you meant to use the type 4 driver. Using the type 2 driver > requires some setup in the DB2 client. Also, there are different driver > classes for the different drivers - so they have to match. > > Jeff Butler > > > > On 6/12/07, mister blinky <[EMAIL PROTECTED]> wrote: >> >> >> I believe i have solved this. Turned out to have been a driver issue. >> >> in the <transactionManager> definition, using this >> >> <property name="JDBC.ConnectionURL" >> value="jdbc:db2://localhost:50000/devdb"/> >> >> rather than this >> >> <property name="JDBC.ConnectionURL" value="jdbc:db2:DEVDB" /> >> >> made the problem go away. >> >> Can somebody explain why? I have been using ibatis to map all fields - >> INTEGER, VARCHARs, etc to my java beans throughout my development process >> on >> this project and have ONLY had an issue with these two clob columns. And >> the >> prob goes away when i change the db URL? Can't say i understand ... >> >> anyway ... thoughts? >> -- >> View this message in context: >> http://www.nabble.com/ArrayIndexOutOfBoundsException-mapping-CLOB-tf3909489.html#a11085899 >> Sent from the iBATIS - User - Java mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/ArrayIndexOutOfBoundsException-mapping-CLOB-tf3909489.html#a11086410 Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
