Re: DB clasical structure violation

> And I would agree with you only too strongly about people deciding "oh
> we'll put the user's social security number in the name field". *BUT*
> how would *you* stop this in SQL? You've just declared "name" to be a
> text field. How do you stop the user putting any old crap in there? otoh
> you *can* stop users putting text into numeric fields like price, for
> example. Been there, done that, sworn blue murder at the silly idiot
> who's caused 10 times more problems than he's solved.

Isn't this what God created CHECK constraints for? On a good enterprise database, you should be able to combine a constraint and stored procedure to check just about anything.

Jerason

--
______________________________________
How to manage your database in one easy step!
http://www.datadino.com