Thapliyal, Deepak wrote:
>Hi,
>
>Assume I have a bank app.. When customer withdraws $10 from his accouint I
>have to do following
> --> update account_summary table [subtract $10 from his account]
> --> update account detail_table [with other transaction details]
>
>Requirement:
> either both transactions should succeed or both transactions should
>be rolled back in case of failure.
>
>Question:
> if my first update succeeds and second fails (say due to space
>errors .. I have inconsistancy ..
>
>
Not if you run the queries as a single transaction.
>Per the thread below stored procedures/functions cannot have commits. I
>assume that means that they will be implicitly commited ??
>
>How do I approach this simple requirment using psql ?
>
>Thx
>Deep
>
>-----Original Message-----
>From: pgsql-general-owner@postgresql.org
>[mailto:pgsql-general-owner@postgresql.org] On Behalf Of Richard Huxton
>Sent: Tuesday, January 13, 2004 4:32 AM
>To: Anton.Nikiforov@loteco.ru
>Cc: pgsql-general@postgresql.org
>Subject: Re: [GENERAL] Parse error help needed...
>
>
>On Tuesday 13 January 2004 12:01, Anton.Nikiforov@loteco.ru wrote:
>
>
>>RH> Remove the "commit" line - functions cannot define their own
>>transactions RH> anyway.
>>Do you know if it will be solved sometime? Or this is architecture
>>dependend problem? I mean that transactions are rulez and very helpful
>>rulez when working with large databases.
>>
>>
>
>Nested transactions are on the todo list, but I don't know when they will
>appear.
>
>
>
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
