From: | Jonathan Bartlett <johnnyb(at)eskimo(dot)com> |
---|---|
To: | Network Administrator <netadmin(at)vcsn(dot)com> |
Cc: | Doug McNaught <doug(at)mcnaught(dot)org>, postgres general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Interfaces that support cursors |
Date: | 2003-10-10 18:25:51 |
Message-ID: | Pine.GSU.4.44.0310101124100.13045-100000@eskimo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Ok, I did see the autocommit flag setting in DBD:Pg when I starting reading up
> on the DBI/DBD interfacing methods so I guess I could recode for that. However,
> how do you "maintain" the current transaction open if your script is writing
> pages to the web. Even in mod_perl I think that there is a commit after the
> script ends, no?
Be careful you don't waste resources by leaving transactions open forever!
You can use something like PersistentPerl to make sure the script doesn't
terminate, but to get the behavior you're looking for you could only have
one script open at a time. You could also do master/worker scripts
communicating through sockets to keep the transaction open.
Jon
>
> --
> Keith C. Perry
> Director of Networks & Applications
> VCSN, Inc.
> http://vcsn.com
>
> ____________________________________
> This email account is being host by:
> VCSN, Inc : http://vcsn.com
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>
From | Date | Subject | |
---|---|---|---|
Next Message | CSN | 2003-10-10 18:37:14 | Re: int1? types? |
Previous Message | Network Administrator | 2003-10-10 18:20:21 | Re: Interfaces that support cursors |