commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Tombs <>
Subject Re: [jelly] What happens if sql:update isn't wrapped with a sql:transaction element?
Date Tue, 19 Dec 2006 19:49:39 GMT
On Tuesday 19 December 2006 19:22, Karr, David wrote:
> I have a large dbinit script written in Jelly.  I ended up having my
> "insert" tag have a sql:update tag inside of a sql:transaction tag.
> This works, but my script is quite large, and I'm wondering about ways
> to optimize it.
> I imagine I could restructure the entire script so that a single
> "sql:transaction" tag wraps everything, and my "insert" tag doesn't use
> update inside an additional transaction.  I imagine that would work, but
> it would make for a heck of a large transaction.
> What would happen if I simply removed the wrapping "sql:transaction"
> element and added the datasource attribute to the sql:update call?
> Would that result in effectively the same thing, making each statement
> autocommit?  This isn't what I want, I just want to understand what this
> would do.
> My back end is Oracle, if that matters.
Can't answer for oracle but I know that on sqlserver if I don't use a 
sql:transaction tag my sql:updates autocommit. I can only assume the same is 
true of Oracle.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message