From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | emilu(at)cs(dot)concordia(dot)ca |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Questions about Rollback - after insert, update, |
Date: | 2005-09-22 20:02:58 |
Message-ID: | 1127419378.30825.79.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 2005-09-22 at 14:59, Emi Lu wrote:
> We are using (struts) ibates to run the transaction. We already setup
> autocommitte = false, and put insert, update, delete into one
> transaction. However, we found data were not rollback successfully.
> Moreover, in our atomic transaction, some operations are not finished
> successfull, but the data are not rollback.
>
> Your inputs are very welcomed!
I would tend to think it's either a bug in struts or jdbc or you're
making some mistake somewhere. I'm not familiar with struts and
postgresql together.
You might try logging ALL your SQL statements and seeing what is
actually being sent back and forth between struts / java and postgresql.
Not sure what else to do, as I use libpq to access postgresql, meaning
no layer between my app and pgsql, like with jdbc / struts.
From | Date | Subject | |
---|---|---|---|
Next Message | Guy Fraser | 2005-09-22 20:16:48 | Re: array_dims array_lower/upper distance |
Previous Message | Emi Lu | 2005-09-22 19:59:22 | Re: Questions about Rollback - after insert, update, |