Re: mod_perl forking and DBD::Pg prepared statement problem

On 31/05/07, Jonathan Vanasco <[EMAIL PROTECTED]> wrote: aaron- I think this may be more of a Maypole design issue than a mod_perl issue -- although there may also be a bit of an application design issue on your part ( which some of your wording suggests ) , and there may be a dbd::pg issue as

Re: mod_perl forking and DBD::Pg prepared statement problem

aaron- I think this may be more of a Maypole design issue than a mod_perl issue -- although there may also be a bit of an application design issue on your part ( which some of your wording suggests ) , and there may be a dbd::pg issue as well. my input: 1: potential issue in you

Re: mod_perl forking and DBD::Pg prepared statement problem

Hi, On 31 mei 2007, at 17:38, jira wrote: Aaron Trevena napsal(a): Hello you wonderful helpful people :) I've just moved a web application (maypole/c::dbi) from one development server to another, previously the code worked fine but now I get : 'prepared statement "dbdpg_1" does not exist' o

Re: mod_perl forking and DBD::Pg prepared statement problem

Aaron Trevena napsal(a): Hello you wonderful helpful people :) I've just moved a web application (maypole/c::dbi) from one development server to another, previously the code worked fine but now I get : 'prepared statement "dbdpg_1" does not exist' on every (prepared) query to the database. I

mod_perl forking and DBD::Pg prepared statement problem

Hello you wonderful helpful people :) I've just moved a web application (maypole/c::dbi) from one development server to another, previously the code worked fine but now I get : 'prepared statement "dbdpg_1" does not exist' on every (prepared) query to the database. There only are two difference