Whether someone uses a CHAIN versus a SELECT doesn't seem to knot my knickers.And just to be clear, this is YOUR set of pet peeves, and is not by itself either "right" or "wrong".
What upsets me more is people not using:Even if you believe in journalling, it's not for all files. Log files, for example, don't need journals.
- ConstraintsProbably the most useful database feature, but still overused, especially when used to implement business logic.
- TriggersThis is the one where it's really a very subjective opinion as to what goes in a trigger and what doesn't. A whole lot of people whose opinions I respect think no trigger should ever update another file. On the other hand, some put all business logic in their triggers. Anyone who knows me know I lean way towards the "less is more" discipline.
- Real date fieldsSee? I knew we'd eventually agree on something.
- nulls, when appropriateThe single most over-used database feature.
However you can continue to ignore all these features and still be using only DDL instead of DDS and SELECT's versus CHAIN's. And, again, you could be using all these feature and still be using DDS instead of DDL and CHAIN's versus SELECT's.And if you ask three database "experts" you'll get four different architectures. In some ways it's not even so much the discipline as it is that you implement it consistently.
It's not the tool - it's the discipline.
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact