| From: | Ed Loehr <eloehr(at)austin(dot)rr(dot)com> |
|---|---|
| To: | Manuel Lemos <mlemos(at)acm(dot)org> |
| Cc: | Lincoln Yeoh <lylyeoh(at)mecomb(dot)com>, tomg(at)admin(dot)nrnet(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Connecting website with SQL-database..... |
| Date: | 2000-04-24 19:10:21 |
| Message-ID: | 39049C1D.64AC33E6@austin.rr.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-interfaces pgsql-sql |
Manuel Lemos wrote:
>
> >Plus if you get a warning/error, Postgresql _requires_ you to rollback,
> >whereas many other databases don't.
>
> That's what Metabase expects. When there is an error, you should rollback
> before exiting a transaction with AutoCommit(Off).
>
> I noticed the discussion but I could not quite figure what was the problem.
The problem on this, from my perspective, is that if you have a transaction
that consists of 20 queries, and the 14th query fails, then you'd like to
be able to abort only the *statement*, recovering in the client application
in whatever way seems appropriate. Automatically *forcing* a rollback
takes that recovery choice away.
Regards,
Ed Loehr
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ross J. Reedstrom | 2000-04-24 19:16:25 | Re: Revisited: Transactions, insert unique. |
| Previous Message | Joachim Achtzehnter | 2000-04-24 18:01:57 | Re: Revisited: Transactions, insert unique. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manuel Lemos | 2000-04-25 05:31:00 | Re: Connecting website with SQL-database..... |
| Previous Message | Manuel Lemos | 2000-04-24 06:32:30 | Re: Connecting website with SQL-database..... |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manuel Lemos | 2000-04-25 05:31:00 | Re: Connecting website with SQL-database..... |
| Previous Message | Manuel Lemos | 2000-04-24 06:32:30 | Re: Connecting website with SQL-database..... |