Re: AW: AW: [HACKERS] TRANSACTIONS - Mailing list pgsql-hackers

From Don Baccus
Subject Re: AW: AW: [HACKERS] TRANSACTIONS
Date
Msg-id 3.0.1.32.20000224085146.0171bb90@mail.pacifier.com
Whole thread Raw
In response to Re: AW: AW: [HACKERS] TRANSACTIONS  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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@pacifier.com> Nature photos, on-line guides, Pacific Northwest Rare Bird Alert
Serviceand other goodies at http://donb.photo.net.
 


pgsql-hackers by date:

Previous
From: Zeugswetter Andreas SB
Date:
Subject: AW: AW: AW: [HACKERS] TRANSACTIONS
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Re: [BUGS] First experiences with Postgresql 7.0