Sagara Wijetunga <[EMAIL PROTECTED]> wrote:
> 
> Is it possible to span a database transaction across
> multiple CGI scripts? That is, start transaction and
> lock some records in one CGI script and update and
> commit in another CGI script.

One possible approach is to set up a separate process that runs in the
background, perhaps as a daemon, and handles all the actual database
requests.  You would use some sort of session identifier in your CGI
scripts, passing it to the background process so it could manage the
requests appropriately.  Each session would get its own connection to the
database so that the transaction locking would be effective.

Ronald


Reply via email to