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 ]

Lecar_red (5694)

  (email not shown publicly)

Journal of Lecar_red (5694)

Thursday April 21, 2005
03:20 PM

I'm digging Class::DBI::mysql

[ #24307 ]
I've been really digging Class::DBI and Class::DBI::mysql.

In a master class (or whatever that main thing would be called), I've been able to do:

  userid INT,
  url varchar(256),


Instead of mysql < setup_my_stuff.sql and other crap...
Very cool. This isn't even mention the easy column -> method mapping...

Thanks, Tony!

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.
  • Yeah, this totally cool. I'm always keeping my table definitions in all my classes like that. No more out-of-date sql files!

    BTW, in production code I add this to my base class:

            *create_table = sub() {0};

    It makes the call a no-op, and that's nice for performance (at least on startup). And it's very very simple.
    • Does that have any different an effect from:

      sub create_table() {0}


      • I was under the impression that it wouldn't trigger warnings, but it does. So there's no difference apparently.

        I now have this:
            no warnings 'redefine', 'prototype';
            sub create_table() {0}
        I'm still a little puzzled by the prototype, though. I seem to remember that this way would get optimized away, so that not even the arguments to the sub would be evaluated. But I'm wrong about that, apparently.
        • Maybe if you put it in a BEGIN block instead of a naked block? And/or ahead of your "use Class::DBI::mysql". The problem is that you're compiling some use of that subroutine before you're compiling this code.
          • Randal L. Schwartz
          • Stonehenge