Mike Mascari <mascarm@mascari.com> writes:
> In fact, some could argue that the default behavior of PostgreSQL
> should be changed (or at least have an option) to behave like
> Oracle, where a transaction is implicitly begun at the first
> encounter of an INSERT/UPDATE/DELETE - or in PostgreSQL's case, the
> first submitted statement.
If we put in an implicit BEGIN at the start of a connection, when
does it get committed? We certainly dare not do an implicit COMMIT
when the client disconnects, but without that the change would
completely break a lot of existing applications.
Personally I'm perfectly happy with the notion that clients who want
this behavior can send a BEGIN for themselves ...
regards, tom lane
