OK, I've uploaded DBA::Backup::MySQL to PAUSE. It didn't get indexed due to a permissions problem. I'll look into that tomorrow and upload a basic top level DBA package documenting the purpose of the name space and referring to this thread. Over the weekend I'll break out the principle backup management portions (scheduling tasks) and upload the DBA::Backup base package.
Thanks again to everyone for your input! If anyone is interested in this project, I would certainly welcome any help, including comments on how you currently manage MySQL backups and log rotations and what you think this tool should be able to do. On Thu, 2004-10-28 at 05:07, Tim Bunce wrote: > > 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. -- Sean Quinlan <[EMAIL PROTECTED]> Massachusetts General Hospital
signature.asc
Description: This is a digitally signed message part
