From: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com> |
---|---|
To: | PostgreSQL <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: transactions and ecpg |
Date: | 2012-09-23 07:29:29 |
Message-ID: | CAAfz9KM8HWcDqmL9O-nv4qBaSR7yThqnhkvbX+55+Z8WRpRq2g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Hey Wayne
2012/9/22 Wayne Cuddy <lists-pgsql(at)useunix(dot)net>
> I'm looking at some code that a coworker ported from Informix to
> Postgres 9.0. The Informix database did not have transaction logging
> enabled thus no begins/aborts/commits/rollbacks where in the original
> code. The way the code has been ported there are still no begin
> statements in the code, only commit and rollback after data changing
> statements are executed.
>
> Question 1: After a commit/rollback does the next SQL statement
> implicitly begin a transaction?
>
Please, read http://www.postgresql.org/docs/9.2/static/sql-begin.html
>
> Question 2: If we're just examining data via SELECT statements should we
> be issuing COMMIT statements after or are they only required for data
> modifying operations?
>
Please, read http://www.postgresql.org/docs/9.2/static/transaction-iso.html
>
> Thanks in advance,
> Wayne
>
--
// Dmitriy.
From | Date | Subject | |
---|---|---|---|
Next Message | Abhijit Prusty -X (abprusty - UST Global at Cisco) | 2012-09-23 14:41:09 | HOw to convert unicode to string |
Previous Message | David Johnston | 2012-09-23 01:50:43 | Re: |