Timeline for Table design for ticket sales
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 12, 2016 at 6:01 | vote | accept | mgaldieri | ||
| May 12, 2016 at 5:50 | comment | added | mgaldieri | Yes, @ziggy-crueltyfree-zeitgeister. Most of the ticket info would be the same for every ticket. Only their serial number must be unique. A ticket batch doesn't really have any meaningful info for my purposes, that I need to keep track of. My application only need to deal with the individual tickets. My concern was more about performance, disk usage, implementation complexity and general best practices applied to this situation. | |
| May 12, 2016 at 0:37 | comment | added | Ezequiel Tolnay | What ticket information would be common to all tickets in a batch? Would most of the information be the same? The use of a TicketBatch table makes sense if you actually have ticket batches (real or virtual), and the batches have a meaningful purpose and you want to record it. | |
| May 11, 2016 at 22:42 | answer | added | Stuart J Cuthbertson | timeline score: 2 | |
| May 11, 2016 at 19:11 | history | edited | Andriy M | CC BY-SA 3.0 |
split into paragraphs for readability, corrected some typos, added minor formatting
|
| May 11, 2016 at 17:39 | review | First posts | |||
| May 11, 2016 at 19:11 | |||||
| May 11, 2016 at 17:37 | history | asked | mgaldieri | CC BY-SA 3.0 |