On Wed, Oct 27, 2004 at 02:28:30PM -0400, Sean Quinlan wrote: > 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 DBA::Backup::MySQL? The DBA name space could then be a catch all > for any tools specifically targeted at database administration tasks, > such as backups.
Um, a DBA namespace sounds reasonable as a home for cross-database DBA support modules. I'd recommend a structure like this: DBA::<activity> -- front-end module DBA::<activity>::* -- support modules DBA::<activity>::Plugin::<databasename> -- back-end modules But... I'd caution that the "market" for DBA-type APIs that'll work across multiple DBs is small. Partly because not many people have significant investment in more than one database of a similar type, but mostly because the lack of standardization of DBA concepts across databases. You'll either end up with a lowest-common-denominator approach that has too little functionality, or have so many database-specific flags an options and whatnot that there's little benefit in having a "common API". Having said that, I'd be happy to see this happen if it did :) Tim.
