Such as ^MySQL::Abstract or ^Oracle? Perhaps the modules belong under ^Persistence? It's an oo persistence framework, or a database application framework.
Honestly, I don't mind changing the naming, but I do care about changing the hierarchy. Naming it ^MySQL::Abstract::DB etc means I have to make several changes to other classes in order to maintain support for more than one type of database. I am sure the premise of these classes is not new, perhaps someone has a pointer to how others have named them? thnx Richard F. Rebel On Wed, 23 Oct 2002 23:01:12 -0500 _brian_d_foy <[EMAIL PROTECTED]> wrote: > In article <[EMAIL PROTECTED]>, Perl Authors Upload Server ><[EMAIL PROTECTED]> wrote: > > > The following module was proposed for inclusion in the Module List: > > > > modid: Automatic::DB > > > Basically I need a namespace for a suite of modules that provide > > the ability to automatically abstract a SQL database. > > what does it mean to automatically abstract something? i suppose > i don't understand either "automatic" or "abstract" in this context. > > i don't think the automatic portion is the proper top level > regardless of the definition. since this deals with databases, > something that starts off with a database top-level name is much > better. > > the next level should say something about what it does with > databases. in this case it makes abstracts. > > beyond that you can talk about how you do it. > > -- > brian d foy (one of many PAUSE admins), http://pause.perl.org >
