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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Heh, my largest database project so far was on a database with data that was so bad that stored procedures were not even realistic due to the amount of special-casing. We couldn't change the schema because legacy applications still did a lot of the work. We made heavy use of accessors and mutators in Perl to make the data look somewhat less hairy to the business logic.

    So, I my responses:

    1) porting: nearly never (almost 100% mysql)
    2) multiple apps: on at least two occasions
    3) db features: not often
    4) damage: yes, but very rarely significant