Linked by Eugenia Loli-Queru on Thu 17th Jun 2004 21:11 UTC
Today we features a mini-Q&A with Alex Roedling, MySQL's Senior Product Manager, about all things MySQL, the competition, technology, licensing and more.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
That's fine, but I would argue that is a very narrow perspective on what a database is and does. You are talking about a database with only one purpose. But, if you have a large general-purpose corporate database, where there often is more than one application involved, as well as possibly more than one administrator, etc... who can perform queries, then that "final line of defense" is absolutely critical.
Also, it's not just about constraints, but about helping the programmer. If the data model and column definitions of your application don't correspond properly with that of the database, MySQL will often *not even provide an error message*, but silently truncate strings, or reduce ints, or add weird defaults, etc... For any sort of serious database work, this ought to send shivers down your spine.