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

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.
  • Comment on Re^4: What do people want from DB abstraction modules?

Replies are listed 'Best First'.
Re^5: What do people want from DB abstraction modules?
by suaveant (Parson) on Jan 05, 2006 at 18:07 UTC
    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)

      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.
        Yeah... being able to use something like date_format in mysql on the query side would probably be the way to go.... I assume most databases can handle it... of course, people should be able to define their date format of choice.

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