Hi
On 30 November 2011 22:30, Kasia Tuszynska wrote:
> With Postgres that is not the case, if the 50th sql statement in a long
> transaction incurs an error, the whole transaction is rolled back for you
> automatically, you the developer have no say in that unless you bracket
> each statement wi
On 11/30/2011 09:19 PM, Nicholson, Brad (Toronto, ON, CA) wrote:
This functionality is something that Postgres can do today. We expose
the ability to do this with explicit savepoints. The difference is
that Oracle allows you to set it on a per transaction basis (I
believe) and it will behave th
Subject: Re: [ADMIN] transaction error handling
On 29 November 2011 21:34, Rob Richardson
mailto:rdrichard...@rad-con.com>> wrote:
If Oracle saves half of the data between the beginning and ending of the
transaction, doesn't that defeat the purpose of the transaction?
It sure e
> -Original Message-
> From: pgsql-admin-ow...@postgresql.org [mailto:pgsql-admin-
> ow...@postgresql.org] On Behalf Of Rob Richardson
> Sent: Tuesday, November 29, 2011 1:35 PM
> To: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] transaction error handling
>
>
>
> On 29 November 2011 21:34, Rob Richardson
> wrote:
>
>> If Oracle saves half of the data between the beginning and ending of the
>> transaction, doesn't that defeat the purpose of the transaction?
>
>
It sure enough kills Atomicity. I can see a use for this on importing data
from external so
I have the same confusion...
于 2011/11/30 2:34, Rob Richardson 写道:
Very naïve question here: Why would you want to save the data from the first
insert?
I thought the purpose of a transaction was to make sure that all steps in the
transaction executed, or none of them executed. If Oracle sav
Very naïve question here: Why would you want to save the data from the first
insert?
I thought the purpose of a transaction was to make sure that all steps in the
transaction executed, or none of them executed. If Oracle saves half of the
data between the beginning and ending of the transact
> -Original Message-
> From: pgsql-admin-ow...@postgresql.org [mailto:pgsql-admin-
> ow...@postgresql.org] On Behalf Of Kasia Tuszynska
> Sent: Tuesday, November 29, 2011 3:35 PM
> To: Kevin Grittner; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] transaction erro
...@postgresql.org] On Behalf Of Walter Hurry
Sent: Tuesday, November 29, 2011 12:50 PM
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] transaction error handling
On Tue, 29 Nov 2011 09:57:24 -0800, Kasia Tuszynska wrote:
> Hi Everybody,
>
> This is an architectural question.
> I a
On Tue, 29 Nov 2011 09:57:24 -0800, Kasia Tuszynska wrote:
> Hi Everybody,
>
> This is an architectural question.
> I am testing on Postgres 9.0.2 on windows and linux(suse, rhel, ubuntu)
>
> I want to make sure that I have the correct understanding of the
> Postgres architecture and would like
On Tue, Nov 29, 2011 at 10:57 AM, Kasia Tuszynska wrote:
> Postgres:
> Begin transaction
> Insert - no error
> Insert - error raised
> Transaction loss = no implicit rollback to the single error free insert.
>
> Is this a correct interpretation of the Postgres transaction error handling?
> If so,
gsql-admin@postgresql.org
Subject: Re: [ADMIN] transaction error handling
Kasia Tuszynska wrote:
> Oracle:
> Begin transaction
> Insert - no error
> Implicit savepoint
> Insert - error raised
> Implicit rollback to the savepoint, no transaction loss, error
> raised on the insert st
Kasia Tuszynska wrote:
> Oracle:
> Begin transaction
> Insert - no error
> Implicit savepoint
> Insert - error raised
> Implicit rollback to the savepoint, no transaction loss, error
> raised on the insert statement that errored out.
> End transaction, implicit commit, with the single error free
Hi Everybody,
This is an architectural question.
I am testing on Postgres 9.0.2 on windows and linux(suse, rhel, ubuntu)
I want to make sure that I have the correct understanding of the Postgres
architecture and would like to enquire if there are any plans to change it.
Comparing Oracle and P
14 matches
Mail list logo
