in reply to Re^2: What do people want from DB abstraction modules?
in thread What do people want from DB abstraction modules?

Well... everything... first of all it should be able to connect to any database and all functionality should be supported transparently. Functionality that isn't in some databases should be supplied by the module. It should be able to push dates and times at you in a consitent and configurable manner. You should be able to describe what you want in english and have it return data $dbe->plaintext_query("Give me all the clients from Schenectady, NY who are past due on their bill"). All functionality that is implemented should act the same, regardless of how the database handles the back end, count, group by, limit etc. Oh.. and it should make good coffee. :)

It would do all this remarkably quickly.

It would be called God::DB ;)

                - Ant
                - Some of my best work - (1 2 3)

Replies are listed 'Best First'.
Re^4: What do people want from DB abstraction modules?
by techcode (Hermit) on Jan 05, 2006 at 17:49 UTC
    Wash dishes for you? How about doing the whole thing (writing Perl code) for you?

    Anyway - I didn't quite planed this as a joke node, so more constructive replies would be great.

    Have you tried freelancing? Check out Scriptlance - I work there.
[reply]
      Yeah... that is why I aplogized when I wrote it :)

      A couple of my points were valid, but a bit pie in the sky. The thing about dates is actually quite relevant, but since I don't use anything like DBIx I can't comment on what is already out there and what it can do.

                      - Ant
                      - Some of my best work - (1 2 3)

[reply]
        Yes date/time fields are nightmare. I agree.

        Latter mentioned Rose::DB has code that translates from Perl format to DB in use format and the other way around.

        I'm planing to support that but still not sure how to implement it. Do it automatically on read/write (behind the scenes) by figuring out if field is date/time - or perhaps export a function (or call as $DB->dt_format($value_here);) for that so it's done manually?

        In case of writing (UPDATE/INSERT) it's not a (performance) problem to do the conversion in Perl, but it would be stupid to loop through all the results just to format the date/time fields. So I guess it should be implemented in SQL itself?

        Have you tried freelancing? Check out Scriptlance - I work there.
[reply]

In Section Seekers of Perl Wisdom