Quoting Jonathan Bartlett <johnnyb@eskimo.com>:
> > 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
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
Absolutely- I was gonna dig into my mod_perl manual since I'm not sure if/how I
can make the HTML interfaces persist in Apache- I know the backend can (Apache
<-> Pg) but instead of increasing the complexity of things this time(all the
script does is write pages of images), I'll see how the selects with
offset/limit modifiers perform. I'm going to check our that Persistent Perl
product for future reference too. Thanks.
--
Keith C. Perry
Director of Networks & Applications
VCSN, Inc.
http://vcsn.com
____________________________________
This email account is being host by:
VCSN, Inc : http://vcsn.com