From: | Björn Lundin <bjorn(dot)lundin(at)swipnet(dot)se> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Transaction processing from a Perl script.... |
Date: | 2002-08-22 20:36:47 |
Message-ID: | ak3hvl$1ks6$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Issue the exec procedure with like
Exec("Begin Work")
Exec("insert into child table 1 ")
Exec("insert into child table 2 ")
Exec("insert into the master table")
Exec("Commit")
check result of commit,
if not everything is ok
Exec("Rollback")
I dont know the exact Perl syntax, but this is how I would go about to do
it...
/Björn
Greg Patnude wrote:
> Ok.... I can connect to my postgreSQL database with Autocommit=>0 to set
> up for a transaction-based process...I'm using Perl 5.6 and Pg 1.9 on a
> FreeBSD 4.x box with postgreSQL 7.2.
>
> The question is HOW should I go about managing the transaction itself from
> within my Perl script... I need to {pseudo}:
>
> --begin work
> --insert into child table 1 (and return the new primary key pk1)
> --insert into child table 2 (and retrun the new primary key pk2)
> --insert into the master table (child 1 pk, child 2 pk) and return the
> master primary key pkm
> --commit work if everything is ok
> --else rollback if anything failed.
>
> Usually, this kind of thing is handled by the connect method (I've
> typically used Oracle, Sybase, or SQL Server with VB, C, or Powerbuilder)
> and the
> {begin {process}{commit or rollback}} is managed by the connect method
> defined in the application. Pg has no such mechanism that I could find in
> the Pg docs...
>
> Any ideas anyone ???
>
> TIA
>
> GP
From | Date | Subject | |
---|---|---|---|
Next Message | Linn Kubler | 2002-08-22 21:11:55 | Formatting date question |
Previous Message | Robert Treat | 2002-08-22 17:32:34 | Re: Installing Booktown Schema |