Re: [Mason] Database connect

[Bjorn S. <bjo...@he...>]

Perrin Harkins writes:

[...]

> That's correct, but the post I responded to was suggesting to do exactly
> that but to write it by hand instead of using Apache::DBI.

Yes, that was a (too) quick suggestion on my part.  Not sure I see how
Apache::DBI fits in, though.  Yes, you use Apache::DBI for the persistent
connection, but you still need a way to get to the DB handle, thus the
globals, instead of doing the superfluous DBI->connect every time.  (It's
a matter of laziness. :-)

> The best thing to do would be to change the application so that a single
> database login could be used.

Definitely.  The assumption was that that was out of the question and
that for some reason he had to go with a per-user connection.  Otherwise,
to avoid running out of resources if there are indeed a lot of users, it
would seem the connection will need to be established and disconnected on
a per-request basis based on userid/pw retained in session info.  Or keep
a connection pool (don't use Apache::DBI then) that holds the connection
for the X most recent users, where X is some maximum number you can allow
with your given hardware, as a variant on my initial suggestion.

Bjorn.