Why are creates auto-committing?

I am new to ibatis and using DAO and sqlMaps. I am trying to perform multiple creates in a function and having them rollback if one of them fails. The rollback does not seem to be performed. Instead the creates up to that point are committed. I apparently am not clear on what controls the

Re: Why are creates auto-committing?

. Sapp [EMAIL PROTECTED] wrote: Using Oracle 10g and the thin driver for it. Also, using Tomcat application server on top of RHEL AS 3. At 09:17 AM 12/22/2004, you wrote: Which RDBMS are you using? On Tue, 21 Dec 2004 15:57:07 -0600, Albert L. Sapp [EMAIL PROTECTED] wrote: I am new

SQL Maps and/or DAO

1. Can someone explain to me how the DAO framework enhances the use of SQL Maps framework or is the DAO framework a replacement for SQL Maps framework? Both of them seem to be used as transaction managers. All I am wanting to do is some transaction processing against a Oracle database using

Turning transaction auto-commit off.

In reading over information on the Oracle JDBC driver, it says that I must use this command to turn auto-commit off. Connection.setAutoCommit(false); In the sql-map-config.xml file, I find this property line. property name=JDBC.DefaultAutoCommit value=true / So I figure all I need to do is

Problem with result mapping.

. --- Cause: com.ibatis.common.exception.NestedRuntimeException: Error setting properties of 'UserDetails: userID = 2 , printedName = ALBERT L. SAPP , mailingAddress1 = SCHOOL OF CHEMICAL SCIENCES , mailingAddress2 = UNIVERSITY OF ILLINOIS , mailingAddress3 = ROOM 320, NOYES LAB, BOX D-2

Re: Problem with result mapping.

to narrow the problem area. once you have done that we might be able to provide you with better insight. On 4/28/05, Albert L. Sapp [EMAIL PROTECTED] wrote: Hi, guys. I have been struggling with this for a while now and can't seem to find where I have things messed up. Here is the error

Re: Using a like statement

Build your value before sending it to the select statement in your xml file. I set my values in my action by using this: itemQuery.setDescription('%' + request.getParameter(description).toUpperCase() + '%') I, then, pass the parameter itemQuery to my manager and DAO layers. Hope this helps.