Re: Vote totals for SET in aborted transaction - Mailing list pgsql-hackers

From Jan Wieck
Subject Re: Vote totals for SET in aborted transaction
Date
Msg-id 200204261322.g3QDMam08818@saturn.janwieck.net
Whole thread Raw
In response to Re: Vote totals for SET in aborted transaction  (Curt Sampson <cjs@cynic.net>)
List pgsql-hackers
Curt Sampson wrote:
> On Fri, 26 Apr 2002, Marc G. Fournier wrote:
>
> > NOTE that I *do* think that #1 is what *should* happen, but there should
> > be some way of turning off that behaviour so that we don't screw up ppl
> > expecting "Oracles behaviour" ...
>
> I don't think this follows. If it's only for people's expectations,
> but we default to #1, their expectations will be violated until
> they figure out that the option is there. After they figure out
> it's there, well, they don't expect it to behave like Oracle any
> more, so they don't need the switch, right?
   Beeing  able  to  "read" is definitely an advantage in the IT   world.  Someone just  has  to  do  it  before
finishing the   implementation based on assumptions :-)
 


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #




pgsql-hackers by date:

Previous
From: Jan Wieck
Date:
Subject: Re: Vote totals for SET in aborted transaction
Next
From: "Marc G. Fournier"
Date:
Subject: Re: Vote totals for SET in aborted transaction