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
petdance (2468)
petdance
andy@petdance.com
http://www.perlbuzz.com/
AOL IM: petdance (Add Buddy, Send Message)
Yahoo! ID: petdance (Add User, Send Message)
Jabber: petdance@gmail.com
I'm Andy Lester, and I like to test stuff. I also write for the Perl Journal, and do tech edits on books. Sometimes I write code, too.
andy@petdance.com
http://www.perlbuzz.com/
AOL IM: petdance (Add Buddy, Send Message)
Yahoo! ID: petdance (Add User, Send Message)
Jabber: petdance@gmail.com
I'm Andy Lester, and I like to test stuff. I also write for the Perl Journal, and do tech edits on books. Sometimes I write code, too.
Friday March 24, 2006
09:51 PM
Database normalization and DRY
From Peter Corlett on the london.pm mailing list
"A relational database is a collection of facts, and normalising them is a way to ensure there are no contradictions. If you think DRY is just a memory-saving optimisation, you've rather missed the point."
What a great way to put it!
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
--Larry Wall in stab.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Yes (Score:2)
Very true, and thank you for sharing this very insightful way of expressing it.
Memory is cheap. Fixing errors is expensive.
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers