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
:
databases:
- mysql
days: Sat
--
Sean Quinlan [EMAIL PROTECTED]
MySQL-Backup-0.8.tar.gz
Description: application/compressed-tar
signature.asc
Description: This is a digitally signed message part
* 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
is
scattered about a bit still, but should be functionally correct.
I would welcome any feedback on the module name. I've got it as
MySQL::Backup at the moment, and don't see anything currently on CPAN
in
that name space. Does anyone have any other recommendations or concerns
before I upload it to PAUSE
Christopher Hicks writes:
On Tue, 26 Oct 2004, Smylers wrote:
... DBIx:: should be for things that are generally usable with DBI,
where the I is independent ...
I agree with Chris much more than Smylers here, but if we go along
with Smylers perspective for a minute then we need /some/
be in a
handful of namespaces it would seem to be advantageous. I'd love to see
see Alzabo. MySQL::Backup, and the other DBI-based modules with strange
names paces all go in DBIx while the other things (oraperl, postgres,
etc.) go into Database::. We have Spreadsheet:: to take care
On Tue, Oct 26, 2004 at 04:34:32PM -0400, Christopher Hicks wrote:
When I read Mark's message I realized his point is what I'd been wanting
to say in the first place; so the more _I_ think about it, the more
DBIx:: seems like a completely inappropriate place for this module!
How is doing a
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 such as
backing up tend not to be database-independent.
if we
by daily cron job. The documentation is
scattered about a bit still, but should be functionally correct.
I would welcome any feedback on the module name. I've got it as
MySQL::Backup at the moment, and don't see anything currently on CPAN in
that name space. Does anyone have any other
11 matches
Mail list logo
