Prev: Invitation to critique a unique stored procedure
Next: Highest and lowest values
From: steve dassin on 7 Jul 2008 05:50
If you're a student of sql I think you'll find two recent threads very
interesting.

microsoft.public.sqlserver.programming
Thursday, June 26, 2008
'update joined tables'
http://tinyurl.com/69hh5c

microsoft.public.sqlserver.programming
Sunday, June 29, 2008
'Storing a collection of lines'
http://tinyurl.com/56dpd4

A number of interesting issues are raised by Joe Celko and others including
the limits of the update operation (why multiple tables can't be updated and
the case of multiple cascade update paths), a one-one requirement
constraint (a master row can't exist without detail rows) and an opposite
constraint among others. My take on these issues, from a relational point of
view, can be found here:

http://beyondsql.blogspot.com/2008/07/justifying-sql-cop-out.html
http://beyondsql.blogspot.com/2008/07/one-one-reference.html
http://beyondsql.blogspot.com/2008/07/opposite-constraint.html

The trick, as always, is to see through the fog :-)


 | 
Pages: 1
Prev: Invitation to critique a unique stored procedure
Next: Highest and lowest values