@Aaron a) simpler foreign keys b) they aren't lookup string, they are 'things' that are modelled - eg label type or carrier, therefor the data will in general be constrained differently and of course you have the flexibility to add columns. c) more specific names. d) 100 is probably an exaggeration e) in complex queries there will be less work for the planner to do as it won't have to guess cardinalities based on the filter - simpler is better for the planner
e) assuming you are doing FKs properly, you will be hard-coding the 'type' into your check constraints - I prefer not to hard-code values in this way but would rather build the relationships into the model f) memorability - it is easier to remember a well named lookup table name than an id or code g) making it easier for there to be a single interface to changing the data means there probably will be one. Even if a single interface is really not the most appropriate.
h) permissions. Perhaps someone should be able to add new 'colours' but not new 'payment methods'
Currently I am modeling a database to be used for vehicle spare parts inventory management and I am stuck...
I have a specific requirement that I do not know how to model in the database and that is that some spare parts can be broken from set into pieces.
Spare can be issued in set or pieces. ...
@SimonRigharts not to me - I can see a bit more about the OP on his profile and I think it is likely a real problem (though homework is allowed too - it should just be tagged of course)
When I'm looking down the front page on dba.se, I often wish I could tell at a glance what happened to the question to bump it there. Sometimes it is obvious from looking at the number of answers, other times you have to follow a link to find out if it has been edited or if an answer has been add...
Top link from this week's newsletter: SQL Puzzles for Teachin': http://dba.stackexchange.com/questions/29/where-are-some-useful-sql-puzzles-to-teach-sql-in-a-workplace See the newsletter: http://eepurl.com/oQBtP
hmmm basically I've three tables blog, users and friends. What I'm trying to get is all the blog posts, all the users and all the blog posts from my friends that suit a LIKE condition
but because of pagination support I need to count all those records to see how many I get in a LIMIT query
Currently I am modeling a database to be used for vehicle spare parts inventory management and I am stuck...
I have a specific requirement that I do not know how to model in the database and that is that some spare parts can be broken from set into pieces.
Spare can be issued in set or pieces. ...
