On Wed, Dec 10, 2008 at 2:27 PM, Justin Wyllie <[EMAIL PROTECTED]> wrote:
> However if Apache uses
> child processes sequentially - i.e there is no danger of that child process
> being used simultaneously by two requests I think I should be ok. I think
> this is what Perrin was confirming?
Yes, th
Hi Guys
Thanks for all the help.
I have some code which inserts something into a database and immediately
(the next line) executes another sql statement with SELECT
LAST_INSERT_ID() - so it is not a previous one from somewhere else in the
code.
My concern was that because the actual connect
On Wed, Dec 10, 2008 at 1:22 PM, Enno <[EMAIL PROTECTED]> wrote:
> yes, but, do you really want to gamble that the second request is handled by
> the same child process? and what if another request comes in between?
I think you're misunderstanding his question. As I read it, he was
worried that m
Perrin Harkins wrote:
On Fri, Dec 5, 2008 at 5:39 PM, Justin Wyllie <[EMAIL PROTECTED]> wrote:
The mySQL documentation for LAST_INSERT_ID says that it returns the last
auto-incremented field value for 'that client'.
I am not sure what the client is in a mod_perl situation with Apache::DBI?
Hi All,
I've migrated Apache-DBI from the Perl Foundation's svn repository to
the Apache Software Foundation svn repository.
From: https://svn.perl.org/modules/Apache-DBI
To: https://svn.apache.org/repos/asf/perl/Apache-DBI
(of course non-committers can use http instead of https).
That said
Hello,
I believe there is an issue with Apache::DBI under mod_perl 2.
Apache::DBI is supposed not to cache connections created in the parent
apache process, since using such a connection from multiple children
simultaneously causes problems. Under MP1 the condition to avoid caching
is
$Apache::S
