From: Richard Jones <rich@annexia.org>
To: Benjamin Geer <ben@socialtools.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] PostgreSQL-OCaml 1.0.1
Date: Fri, 30 Jan 2004 13:22:26 +0000 [thread overview]
Message-ID: <20040130132226.GA32353@redhat.com> (raw)
In-Reply-To: <401A548B.2090603@socialtools.net>
On Fri, Jan 30, 2004 at 12:56:43PM +0000, Benjamin Geer wrote:
> Richard Jones wrote:
> >It throws Sql_error when it can determine an error.
>
> Another thing I forgot to bring up about error handling. If an error
> occurs, you generally want to roll back the transaction. If you're
You might want to have a look at the code to see if it does what you
want.
In practice, writing mainly CGI scripts and standalone scripts as we
do, this is never a problem for us. Our code is structured like this:
let dbh = (* open connection, or get connection from pool *)
(* do work with the connection, never checking for any exceptions *)
dbh#commit
In the case of a standalone script, the script dies (exits) when an
error occurs, printing the SQL error message. The database then
automatically rolls back the connection. This is just the behaviour
of PostgreSQL - if a connection is closed in the middle of a
transaction then the database gets rolled back.
In the case of CGI scripts, the Dbi Pool code automatically performs a
dbh#rollback just before taking back a connection and placing it back
into the pool. So if an error did occur before the commit, then the
database gets rolled back.
Rich.
--
Richard Jones. http://www.annexia.org/ http://www.j-london.com/
Merjis Ltd. http://www.merjis.com/ - improving website return on investment
http://www.YouUnlimited.co.uk/ - management courses
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-01-30 13:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 12:02 Richard Jones
2004-01-30 12:15 ` Benjamin Geer
2004-01-30 12:23 ` Richard Jones
2004-01-30 12:30 ` Richard Jones
2004-01-30 12:43 ` Benjamin Geer
2004-01-30 12:56 ` Benjamin Geer
2004-01-30 13:22 ` Richard Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-28 18:32 Markus Mottl
2004-01-28 22:44 ` Stefano Zacchiroli
2004-01-28 23:21 ` Markus Mottl
2004-01-29 9:38 ` Sven Luther
2004-01-29 18:18 ` Alain.Frisch
2004-01-29 20:06 ` Richard Jones
2004-01-29 23:36 ` Markus Mottl
2004-01-30 5:50 ` Josh Burdick
2004-01-30 7:37 ` Shawn Wagner
2004-01-30 8:21 ` Vitaly Lugovsky
2004-01-30 10:24 ` Benjamin Geer
2004-01-30 10:47 ` Richard Jones
2004-01-30 14:58 ` Gerd Stolpmann
2004-01-30 15:46 ` Richard Jones
2004-01-30 11:14 ` Markus Mottl
2004-01-30 11:25 ` Vitaly Lugovsky
2004-01-30 11:41 ` Benjamin Geer
2004-01-30 16:44 ` Alex Baretta
2004-01-30 16:49 ` Benjamin Geer
2004-01-30 8:23 ` Alain.Frisch
2004-02-01 21:03 ` Alain.Frisch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040130132226.GA32353@redhat.com \
--to=rich@annexia.org \
--cc=ben@socialtools.net \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox