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.

use Perl

All the Perl that's Practical to Extract and Report

Database "Design" More | Login | Reply

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

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Database design made too easy (Score:2)

by dws (341) on 2004.04.03 14:22 (#29879) Homepage Journal

Easy-to-use tools (e.g., Access) and the ready availability of books and articles has lowered the starting bar for doing database work, but many of the intro books--at least the ones that I've paged through--seldom give explicit guidance for distinguishing good relational designs from bad ones. The more serious books do, but these aren't often the ones people find on the bookstore shelves when they have a problem to solve, but no background in theory to guide them. And once they have something working, most potential purchasers of the result don't have the technical ability to vet the product.
I think that for the time being, it is our lot in life to discover and clean up such messes.

Reply to This

Get More Comments

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