On Mon, 14 Jul 2003, Mike Mascari wrote:
> Jörg Schulz wrote:
>
> >>... I have this feeling the reason Oracle gives this result may
> >>be again because transactions have been switched off!
> >
> > This snippet comes from the Oracle console:
> > (table name is "a" not "test" / messages are in german)
> >
> ...
>
> > SQL> select * from a;
> >
> > A
> > ----------
> > 1
> > 3
> > 4
> > 2
>
> Presumably Oracle is not rolling back a duplicate key violation,
> allowing the transaction to continue. This is an often requested
> feature not present in PostgreSQL.
Bug. Not Feature
Transactions must be all or nothing. If one step fails for what
ever reason all steps must be failed and rolled back. While in this simple
case ignoring the statment may look fine in more complex examples (where
the is more data in the table...) this can mean data loss and massive
problems!
Peter Childs
>
> Mike Mascari
> [EMAIL PROTECTED]
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
