... created implicitly are pain in the ass.
Note to myself: ALWAYS explicitly name your default constraints, otherwise altering/dropping columns across different servers becomes major headache.
P.S. Not mentioning that system tables that can be used to find implicit constraints change between SQL Server releases...
P.P.S This link helps.
Friday, October 31, 2008
Wednesday, October 8, 2008
Strongly Typed Collections or lets party like it's 1999
Strongly Typed Collections. Great idea. Of course one can argue that if whole code is under your control you should always know what you are adding, but hey, extra sanity check. Can't go wrong with it. Still rather great idea....
... or it was back in 1999. Since then most used languages implemented a next big thing - generics. Even Java that usually drags its feet due to highly collaborative nature of its development did it in the release before last (1.5 if I'm not mistaken). So why our offshore team just checked in brand new strongly typed collection implementation? I know timezones and such, but being years behind? Just another WTF in that looooong list.
... or it was back in 1999. Since then most used languages implemented a next big thing - generics. Even Java that usually drags its feet due to highly collaborative nature of its development did it in the release before last (1.5 if I'm not mistaken). So why our offshore team just checked in brand new strongly typed collection implementation? I know timezones and such, but being years behind? Just another WTF in that looooong list.
Subscribe to:
Posts (Atom)