Sean Quinlan writes:
On Tue, 2004-10-26 at 14:40, Mark Stosberg wrote:
I understood 'DBIx' to be DBI extensions, which is not what this
is.
Correct. This module specifically uses tools provided with MySQL for
managing administration (mysqladmin and mysqldump), and does not use DBI
at
On Tue, 2004-10-26 at 19:32, Christopher Hicks wrote:
On Tue, 26 Oct 2004, _brian_d_foy wrote:
In article [EMAIL PROTECTED], Smylers
[EMAIL PROTECTED] wrote:
I think the opposite -- that DBIx:: should be for things that are
generally usable with DBI, where the I is independent. Things
* Smylers Smylers at stripey.com [2004/10/27 07:13]:
Yes, it might've been better if everything in MySQL:: had been called
Database::MySQL::whatever.
To take the discussion in a different direction for a moment, I'm not
sure that I agree that everything in MySQL:: should be in
On Tue, Oct 26, 2004 at 07:32:29PM -0400, Christopher Hicks wrote:
On Tue, 26 Oct 2004, _brian_d_foy wrote:
In article [EMAIL PROTECTED], Smylers
[EMAIL PROTECTED] wrote:
I think the opposite -- that DBIx:: should be for things that are
generally usable with DBI, where the I is independent.
On Wed, 2004-10-27 at 11:09, Tim Bunce wrote:
So I think MySQL:: is an appropriate place for a module for backing up
'MySQL' databases.
I agree. There are similar namespaces for several other databases.
But now I've got ideas for generalizing it bouncing around in my head!
;-}
Perhaps
