From: | Don Baccus <dhogaza(at)pacifier(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, "'hackers'" <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: AW: AW: [HACKERS] TRANSACTIONS |
Date: | 2000-02-24 16:51:46 |
Message-ID: | 3.0.1.32.20000224085146.0171bb90@mail.pacifier.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At 11:34 AM 2/24/00 -0500, Tom Lane wrote:
>We ought to consider ways of providing the same behavior in psql,
>but it's not gonna happen for 7.0 --- too big a change for beta.
Oh, yeah, no doubt about that.
>> I suspect that most applications don't notice the difference. Most
>> will catch errors and roll back the current transaction, because that's
>> the logical thing to do in most cases.
>
>You are assuming that the app has the intelligence to do so. A psql
>script, for example, lacks that intelligence.
I did say "most", not "all".
>
>I do agree that this is an area where we need to do some work, but
>it's not going to be a simple or small change. We will need nested-
>transaction support in the backend, and some very careful rethinking
>of the client interfaces to try to avoid breaking existing apps.
Well...Oracle provides "autocommit" as a convenience. Perhaps we
could let the user select between old-style or SQL92-compliant behavior
during a transition period?
- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
Nature photos, on-line guides, Pacific Northwest
Rare Bird Alert Service and other goodies at
http://donb.photo.net.
From | Date | Subject | |
---|---|---|---|
Next Message | Zeugswetter Andreas SB | 2000-02-24 16:53:54 | AW: AW: AW: [HACKERS] TRANSACTIONS |
Previous Message | Tom Lane | 2000-02-24 16:48:06 | Re: [HACKERS] Re: [BUGS] First experiences with Postgresql 7.0 |