Given that it's got wide functionality I'd suggest that you give it an
abstract name (ala Alabazoo, Tangram etc) rather than try to find a
name that describes the functionailty specifically.
Tim.
On Wed, Aug 29, 2001 at 10:08:23PM -0700, Jeremy Zawodny wrote:
> Some of you may recall my "DBIx:: namespace?" post from several weeks
> back. Now that I'm convinced that the module we're ("we" being
> "Yahoo!") looking to release belongs there, I need a name for it.
> And I'm not too good at coming up with names, so I'll describe sort of
> what it does and see if anyone is inspired (or at least more inspired
> than I am).
>
> This module is or does the following:
>
> * Provides a wrapper around DBI which makes it really really easy to
> build applications that use MySQL. It caters (to a degree) to
> folks that don't deal with databases much at all and don't want to
> learn DBI's API. But it has some advanced features, too.
>
> * It is currently MySQL-specific, but may not be. There was a bit
> of discussion about Oracle support.
>
> * Gives you very short, intuitive names that wrap existing DBI
> functionality. $db->Hashes($sql) will give you a list of
> hashrefs, for example.
>
> * Provides a simple and consistent error handling mechanism.
>
> * Provides mechanisms for dealing with database servers that are
> temporarily unavailable because of a flaky network or whatever
> other reason. Can auto-reconnect, sleep, or die immediately.
>
> * Can notify (e-mail, page, etc) someone when an application is
> unable to reach the database server.
>
> * Makes it easy to have something like ODBC DSNs on Unix. You can
> name a set of connection parameters (user, host, password,
> database) and use that name in many apps. If the parameters
> change, you make the change in one place.
>
> * Allows you to call native DBI methods, as some "advanced" or more
> seasoned with DBI folks will want to do. It doesn't sub-class
> DBI, but knows how to delegate those calls.
>
> * Provides a way for an application to request a connection to a
> slave (or replica) database server for read-only queries.
>
> * Other stuff that I'm probably forgetting.
>
> My goal is to clean the code up enough so <plug>that I can release it
> in time for my presentation at the Open Source Database Summit.</plug>
>
> http://www.osdn.com/conferences/osdb2/
>
> Would the DBI list be a better place to discuss this, maybe?
>
> Name suggestions? Thoughts? Feedback? Questions?
>
> Jeremy
> --
> Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo!
> <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/
