Ray
Mahnahmahna
Premium
join:2001-04-02
Mesa, AZ
| reply to jayco437
Re: MySQL How to structure database?
said by jayco437  :said by aSic :So should I create a (seemingly infinite amount of) table for each unique class (date), with rows that contain the name/address/etc data? ...and just regularly drop the old tables (classes) as time passes? No. No. No. Create a table, CLASSES. Create a table USERS. Use a "lookup" table, CLASSES_USERS to show which users are signed up for which class. This would allow for users to sign up for multiple classes using the same information. Couple other ways to do it, but creating tables for each class is a no-no. When your table names contain data, that's a code smell. 
--
ON DELETE CASCADE |
|
jayco437
Premium
join:2001-08-11
Lincoln, NE | Interesting read. I'd never heard of the phrase before, but certainly understand what they're talking about. I like the taxonomy of the different "smells" there. All very common problems (or, solutions? that create more problems) |
|
Tenar
join:2008-01-02
Midland, ON
| said by jayco437 :Interesting read. I'd never heard of the phrase before, but certainly understand what they're talking about. I like the taxonomy of the different "smells" there. All very common problems (or, solutions? that create more problems) Yeah an interesting term, I've heard it used in a few blogs here and there. probably related to "information scent" from the SEO world.  |
|
