|
|
Posted by --CELKO-- on 03/24/06 06:35
>> Microsoft has a reputation for being very careful of protecting backwards compatibility by not changing software behavior that developers have come to rely on, whether that behavior was documented or not. At the very least this should be included in the migration white paper as an issue to look out for. <<
Actually, SQL Server has been pretty about getting in line with
ANSI.ISO Standards -- OUTER JOINs, the ALL() predicate, etc.
No obligation to document on the part of a vendor? I have mixed
feeling about that .. and a lawyer! And a user group!
But any developer who codes based on needless proprietary features is
a an amatuer or a hillbilly who cannot speak the language properly.
Anyone who depends on undocumented proprietary features is a dangerous
moron. And, yes, those bad programmers will have to clean up their
crap in dozens of places. This is how Ghod punishes you for your bad
code.
Or how Satan punishes the next guy for YOUR mistakes when he has to
maintain it. A professional would have written code for the next guy.
The amateur amuses himself.
Navigation:
[Reply to this message]
|