We're currently considering shifting our core mod-perl system here at
work to use Class::DBI, since many of the classes we have already are
pretty much reinventing its wheel, and we currently have the time and
space to make a few structural changes before the next development
onslaught begins.
On Fri, 2003-02-07 at 17:34, Simon Batistoni wrote:
We're currently considering shifting our core mod-perl system here at
work to use Class::DBI, since many of the classes we have already are
pretty much reinventing its wheel, and we currently have the time and
space to make a few structural
On Fri, Feb 07, 2003 at 05:34:39PM +, Simon Batistoni wrote:
What do other people do? Just connect using a user with full
privileges, regardless of the script's task? I can't see huge security
disadvantages in this, particularly as such users are locked down to
only take connections from
On Fri, Feb 07, 2003 at 08:00:07PM +, Shevek wrote:
On reading the code, this is sufficient. Don't call set_db at all. This is
pretty close to the architecture I used to use: Each class was responsible
for providing an appropriate DB handle on demand. If you don't call
set_db, and just
