| From: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)ihs(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Vote totals for SET in aborted transaction |
| Date: | 2002-04-29 15:29:56 |
| Message-ID: | 3CCD66F4.6E4877CA@fourpalms.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I've been thinking this over and over, and it seems to me, that the way
> SETS in transactions SHOULD work is that they are all rolled back, period,
> whether the transaction successfully completes OR NOT.
Very interesting! This is a *consistant* use of SET which allows
transactions to be constructed as self-contained units without
side-effects on subsequent transactions. Beautifully powerful.
- Thomas
I've got some other thoughts on features for other aspects of schemas
and table and query properties, but this proposal for SET behavior
stands on its own so I'll hold off on muddying the discussion.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-04-29 15:30:35 | Re: Vote totals for SET in aborted transaction |
| Previous Message | Tom Lane | 2002-04-29 15:25:11 | Re: pid gets overwritten in OSX |