Add a comment

 

Re: The joy of sets

Of course you're right! As you point out, there're a lot of "ifs" between where most schemata are and throwing the RDBMS away.

Clever coding is sometimes (frequently?) used to get around problems with the schema, not problems with the data. My concern is that the code is changed by virtue of its ease of modification rather than it being the right design choice; by doing that you may be implementing features of the database (or its costly extensions!) that you're not even aware of. Hence my deference to an experienced batch developer.

It's worth noting that the situation you describe will lead to duplicate rows, not missing rows - the consequences of the former are often far more tolerable, especially with static data like SKU-level items.


Re: The joy of sets


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).