Timeline for Best approach to design a database model for this situation? Clients and records
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 16, 2012 at 20:02 | vote | accept | aesptux | ||
| Jul 13, 2012 at 12:49 | answer | added | Joel Brown | timeline score: 0 | |
| Jul 12, 2012 at 19:31 | comment | added | aesptux | They represent data like phone numbers, control codecs, etc | |
| Jul 12, 2012 at 18:25 | comment | added | Neil McGuigan | What do the records represent? | |
| Jul 12, 2012 at 17:35 | comment | added | aesptux | Well, it could be a solution, although as you say is not normalized.... Maybe two tables, clients and completeRecord. 1-N relationship, and I can query the same way, with clientCode and dateReceived | |
| Jul 12, 2012 at 16:46 | comment | added | NoChance | I am not sure how you will use the final database, but why not store your data in 1 table? I know it is not a normalized solution, but how does that affect your case? | |
| Jul 12, 2012 at 16:39 | history | asked | aesptux | CC BY-SA 3.0 |