Re: Connecting to an existing transaction state. - Mailing list pgsql-general

From Francisco Reyes
Subject Re: Connecting to an existing transaction state.
Date
Msg-id e91fd9d0e3ecbd2fd9934bd956133965@stringsutils.com
Whole thread Raw
In response to Connecting to an existing transaction state.  (Alex Gen <alexigen@yahoo.com>)
List pgsql-general
On 10:37 am 07/28/08 Alex Gen <alexigen@yahoo.com> wrote:
> 3. Using m01-s2.sql I would like to execute a certain SQL statement
> – BUT within the scope of the transaction begun by m01-s1.sql.

I believe that is not possible.
Specially if you are within a transaction on each of the scripts.

As far as I know all the work getting done inside a transaction is ONLY
visible to that transaction. It would actually be pretty bad if the
database allowed a process to see an uncommited state from a transaction
that may end up rolling back.

What are you trying to test?
You mentioned how you are testing, but what is the business need? Or
business concern?

ie It could be something like.. we are concerned that if we run these two
scripts one may lock the other.


pgsql-general by date:

Previous
From: "Francisco Reyes"
Date:
Subject: Re: Problem running script
Next
From: Stephen Frost
Date:
Subject: Re: Must be table owner to truncate?