Search Postgresql Archives
Atomicity in DB transactions (Rollback related)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: pgsql-general@xxxxxxxxxxxxxx
- Subject: Atomicity in DB transactions (Rollback related)
- From: "Jasbinder Singh Bali" <jsbali@xxxxxxxxx>
- Date: Mon, 18 Jun 2007 11:45:17 -0400
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=JoligNMxMtjUv5yr7cin+G37rkZFbh7drSUyMVximr8Lyffp3+80e4H+126231iYeBJZ1yrPOkSDashhBSvENzAX0GGdQGtU26GFY8FVpnslWC9OAxy05hrVflQBOMbuU6jB399PsKlfyiTzQpe9h8c/YO2ITXjhFH75SC3MqS8=
Hi,
I have a Pl/Perlu function in which I have a statement like this:
*******************
my $query_tbl_l_header = $dbh->prepare("SELECT sp_insert_tbl_l_header(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)");
my $exec_l_from =$query_tbl_l_header->execute($unmask_id,$from,$to,$sender,$subject,$replyto,$cc,$bcc,$messageid,$inreplyto,$reference,$mversion,$con_type,$con_id,$con_des,$con_enc,$con_length,$con_dis);
*******************
even if this execute, that calls a function sp_insert_tbl_l_header, fails,
subsequent trasactions continue without failing the whole perl function there and then and makes the Db inconsistent.
Shouldn't the whole function fail and exit at that particular failure and don't continue?
Please let me know how do these transactions work in postgres.
Thanks,
Jas
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]
[Postgresql Jobs]
[Postgresql Admin]
[Postgresql Performance]
[Linux Clusters]
[PHP Home]
[PHP on Windows]
[Kernel Newbies]
[PHP Classes]
[PHP Books]
[PHP Databases]
[Postgresql & PHP]
[Yosemite]