Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Keeping silent 1 Comment More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • two things (Score:2, Insightful)

    by derby (3342) on 2003.03.18 9:03 (#18025)
    1. I don't necessarily agree with your stance but I respect your opinions and I have no problem with you airing them here.

    2. I too work with a very SQL intensive web app and I'm convinced that no matter where the SQL winds up (cgi, modules, stored proc), it ends up being a big ball of mud. It takes a lot of planning and a lot of discipline to keep the SQL where you've decided to keep it. Too many times we look for technical solutions (stored procs, Class::Phrasebook, etc) where manual solutions (design and code reviews) are best.

    -derby

    --
    -derby
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.