Re: Vote on SET in aborted transaction
Hiroshi Inoue <inoue@tpf.co.jp>
From: Hiroshi Inoue <Inoue@tpf.co.jp>
To: Michael Loftis <mloftis@wgops.com>
Cc: Jan Wieck <janwieck@yahoo.com>, Tom Lane <tgl@sss.pgh.pa.us>, Thomas Lockhart <lockhart@fourpalms.org>, Bruce Momjian <pgman@candle.pha.pa.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2002-04-25T02:20:58Z
Lists: pgsql-hackers
Michael Loftis wrote: > > Hiroshi Inoue wrote: > > >Where's the restriction that all objects in a schema > >must be created in an transaction ? Each user has his > >reason and would need various kind of command call sequence. > >What I've mainly insisted is what to do with errors is > >users' responsibilty but I've never seen the agreement > >for it. So my current understanding is you all > >are thinking what to do with errors is system's > >responsibilty. Then no matter how users call commands > >the dbms must behave appropriately, mustn't it ? > > > IMHO as a user and developer it's more important to behave consistently. > A rollback should cause everything inside of a transaciton block to > rollback. Where does the *should* come from ? The standard says that changes to the database should be put back but doesn't say everything should be put back. regards, Hiroshi Inoue http://w2422.nsk.ne.jp/~inoue/