Chris Dolan writes: > Assuming it is based on DBI at its core, your module would fit better > in the DBI extension area. I think DBIx::Backup::MySQL would be good, > as it would leave room for expansions to databases other than ::MySQL.
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. DBIx:: is an appropriate namespace for modules such as DBIx::SearchBuilder, whose target audience is somebody using DBI (possibly with 'MySQL') but wants help with building searches; it's assisting with, or replacing direct use of, DBI. But backing up is a self-contained task, that is to some extent 'out of band' of normal interaction with the database. Somebody wanting to back up a DB is not particularly likely to be thinking of it as a DBI operation. If a back-up module uses DBI internally, I'd consider that an implementation detail and not something that needs advertising in its name. So I think MySQL:: is an appropriate place for a module for backing up 'MySQL' databases. Smylers
