Just my opinion, but I prefer numeric keys that the users *can't*
see, to alpha keys that the users can see:
1. numeric keys are faster
2. using numeric keys that the user can't see allows you
to open up(for UPDATE) ALL the fields that the user can see
including a field like School N
Think of the tables in your database as linked sets.
I have a college database where school description as info associated
in three other tables, allowing one school description, one or more
contacts, requirements for one or more programs, and each program has
one or more degrees associated, i
Hello,
I tend to do either what Hardy suggested depending on the needs of your
database. If the trouble ticket table is to be associated with both
faculty and staff, and that fac/staff can have more than one trouble
ticket I like to create a relational table.
To do this you create a separate ta
Try going to www.mysql.com and search for "foreign key" in the
search box - I found 28 matches - here are the 1st 3 matches:
1. MySQL Manual | 5.4.5 Foreign Keys [4]
2. MySQL Manual | 5.4.5.1 Reasons NOT to Use Foreign Keys constraints [4]
3. MySQL Manual | 9.3.6 Using Foreign Keys [4]
MySQl does not support FK relationship constraints. meaning that if you put
a value in a FK, it won't automatically check to make sure it's a valid
value in the related table. You can, however use FK's. That is how you
should related your tables. It is up to you, the developer, to make sure
that n
