In article <[EMAIL PROTECTED]>, Richard F. Rebel
<[EMAIL PROTECTED]> wrote:
> Such as ^MySQL::Abstract or ^Oracle?
>
> Perhaps the modules belong under ^Persistence? It's an oo persistence framework, or
>a database application framework.
Persistence isn't good either.
you don't' want to name
Hello Brian,
Well, I see your point I guess.
I am abstracting the whole interface to the database in an attempt to keep from
needing SQL littered all over your code and to make it easier to change columns etc
without having to re-code everything, especially when it comes to strong data-typing.
In article <[EMAIL PROTECTED]>, Richard F. Rebel
<[EMAIL PROTECTED]> wrote:
> I am abstracting the whole interface to the database in an attempt to
> keep from needing SQL littered all over your code and to make it
> easier to change columns etc without having to re-code everything,
> especially
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 t
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
