Timeline for SQL schema for movie rating and seenlist
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 16, 2018 at 6:20 | history | rollback | android_dev |
Rollback to Revision 2
|
|
| Dec 16, 2018 at 6:19 | history | rollback | android_dev |
Rollback to Revision 1
|
|
| Dec 16, 2018 at 6:12 | vote | accept | android_dev | ||
| Dec 16, 2018 at 6:02 | history | edited | android_dev | CC BY-SA 4.0 |
added 115 characters in body
|
| Dec 16, 2018 at 5:47 | vote | accept | android_dev | ||
| Dec 16, 2018 at 5:47 | |||||
| Dec 16, 2018 at 5:44 | history | edited | android_dev | CC BY-SA 4.0 |
added 3 characters in body
|
| Dec 16, 2018 at 5:43 | vote | accept | android_dev | ||
| Dec 16, 2018 at 5:47 | |||||
| Dec 16, 2018 at 0:37 | answer | added | Rick James | timeline score: 0 | |
| Dec 15, 2018 at 22:27 | comment | added | LowlyDBA - John M | I would caution against using unobvious values to indicate states that are in conflict with the column name, i.e. using a rating column to actually indicate if a movie was seen or not. Each distinct data point should be a separate column. You can probably be fine using one or two tables, you might want to think about your queries you'll be running and if you would see improvements from querying the data separately or not. | |
| Dec 15, 2018 at 21:52 | history | asked | android_dev | CC BY-SA 4.0 |