Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Matts (1087)

  (email not shown publicly)

I work for MessageLabs [] in Toronto, ON, Canada. I write spam filters, MTA software, high performance network software, string matching algorithms, and other cool stuff mostly in Perl and C.

Journal of Matts (1087)

Monday January 07, 2002
05:05 AM


[ #1958 ]

Oh dear. Seems like my advice to Terrence Brannon about not calling his module "DBIx" fell on deaf ears. And he also seems to have credited me with the code, whereas it was actually autarch that wrote those DBI utility functions that I include in DBIx::AnyDBD's example files. Gah. Writing a DBI abstraction layer seems to be the next right of passage after writing a template processor (both of which I've done).

I wonder if "XML Parser" will be the next thing everyone and her mate will want to write...

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • We wrote our DBI abstraction layer BEFORE writing our templating code (well, to be fair, we mostly just use Template, with a few additions). But concerning our DBI layer, at least we had the good sense to not release it as a separate generalized module for others to use. :-)
  • That code's been in a lot of places!

    First, I wrote something like it for my first programming job.

    Then, I rewrote some of it for the bottom level of Alzabo (the Alzabo::Driver class). But when we were working on WebBoard UX (fuck you, Chatspace!) I took some of it and used it there.

    I didn't realize you had included it with DBIx::AnyDBD but that's cool. And now for some insane reason Terrence thought a DBIx module was needed (Terrence, put down the crack pipe. Its bad for you) and used it once again