When there are no statement, iBatis throws an exception.

I have some insert statement like the follwoing... INSERT INTO TMLBC060 ( USER_ID, RIGHT_CODE, SERVICE_CODE, SERVICE_SHARE ) VALUES ( #p_user_id#, #p_share_right_code#, #p_share_service_code#, #p_share# ) When p_share property is empty, IdInsert has no statement

RE: When there are no statement, iBatis throws an exception.

Can't you evaluate the condition prior to making a call to you map e.g if(map.get("p_share")!=null) sqlmap.insert("idInsert",map); Steve. From: KwonNam Son [mailto:[EMAIL PROTECTED] Sent: Thu 27/10/2005 09:27 To: iBatisUser Subject: When there are no statem

RE: calling trim() on sql map returned strings

I could do it that way... I could also put a type handler on every single string column I get back from the database... The reason I don't really want to do either is because I've got a lot of tables and a lot of POJOs, and doing either is a pain in the neck. Also, I normally write my domain ob

RE: calling trim() on sql map returned strings

Would you agree that being able to replace the default String type handler would make your life easier? --- Gareth Moorst <[EMAIL PROTECTED]> wrote: > I could do it that way... > I could also put a type handler on every single string column I get > back from the database... > > The reason I don'

RE: calling trim() on sql map returned strings

Absolutely. -Original Message- From: Ron Grabowski [mailto:[EMAIL PROTECTED] Sent: 27 October 2005 14:10 To: user-java@ibatis.apache.org Subject: RE: calling trim() on sql map returned strings Would you agree that being able to replace the default String type handler would make your life

Re: how to map unsigned bigint in MySql to long value

I've tried your exact example (as close as I can replicate), and don't have any errors - and the values comes back as expected.  MySql returns a Long for signed bigint fields, and a BigInteger for unsigned bigint fields.   If your database field is unsigned, then you must set the type in your POJO

Open Connections with WAS 6.0

Has anybody had issues with too many open connections using iBatis SIMPLE datasources and IBM WebSphere Application Server 6.0? One of my developers has an application that uses a mixture of iBatis and native JDBC connectivity. When he tests with WAS 5.1 there are only a handful of open connectio

Stored Procedures

Hi everyone. I'm having this problem and i have no idea of how solve it. I have a stored procedure that makes some inserts and updates, besides create temp tables ..., that returns some data after all. It's something like that: CREATE PROCEDURE sp_return_venc ... ... INSERT INTO .. UPDATE..