Can anyone think of any reason NOT to do it this way, but to denormalize
my data and add a few sets of columns in ther main table for this data?
Can anyone think of any reason NOT to do it this way, but to denormalize my data and add a few sets of columns in ther main table for this data?
Only if you're using a database which doesn't allow cascading deletes. Quit often it makes sense when using cripped database systems which aren't quite relational.
Only if you're using a database which doesn't allow cascading deletes. Quite often it makes sense when using cripped database systems which aren't quite relational.
I don't know if any general-use systems fit this bill anymore though, iirc even
MySQL has this.
Only if you're using a database which doesn't allow cascading deletes.
I don't know if any general-use systems fit this bill anymore though,
iirc even MySQL has this.
mySQL (at least last time I worked with it, early 5.x versions) queries
with joins are exceedingly slow.. so that may still affect desire to denormalize. In any case, when views are available, may not be worth debating depinding on use...
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 325 |
Nodes: | 10 (0 / 10) |
Uptime: | 135:54:57 |
Calls: | 501 |
Messages: | 218440 |