enforcing transaction mode for read-write queries.

From: Rajesh Kumar Mallah <mallah(dot)rajesh(at)gmail(dot)com>
To: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: enforcing transaction mode for read-write queries.
Date: 2012-10-01 02:22:58
Message-ID: CAHAX669XR2yhxyKobd2oNESE7Qw0Ak4H-nAM7rCrqYg6czytNg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi ,

We are a PerlDBI shop and and are doing a code migration from
implicit transaction mode (ie, AutoCommit=>0) to an explicit mode (ie,
AutoCommit=>1) .

While the code migration is ongoing (or even permanently) We wish that
postgresql reject
any UPDATE , DELETE , INSERT , nextval , setval etc unless the session is
in a transaction
mode . ie they should be preceded by an explicit "BEGIN work;". This shall
immensely help
us to prevent many bugs in the migration.

Is there any way to accomplish that ? Any help shall be greatly appreciated.

regds
Rajesh Kumar Mallah.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David Johnston 2012-10-01 03:24:13 Re: enforcing transaction mode for read-write queries.
Previous Message Ondrej Ivanič 2012-10-01 01:35:50 Re: transitive pruning optimization on the right side of a join for partition tables