Timeline for MySQL Database Schema for Train Timetables
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 20, 2012 at 19:43 | answer | added | Chris Saxon | timeline score: 7 | |
| Dec 16, 2011 at 21:25 | history | edited | RolandoMySQLDBA | CC BY-SA 3.0 |
added 14 characters in body
|
| Feb 23, 2011 at 11:23 | history | tweeted | twitter.com/#!/StackDBAs/status/40371093168459776 | ||
| Feb 23, 2011 at 2:52 | comment | added | Vicsig | The example given is the output. The sort of queries I would run would be to output: train times at station X, timetable for train Y or all train timetables (example given). Ie a filter effect. | |
| Feb 23, 2011 at 1:24 | comment | added | Joe | Oh ... and I'd likely look to see how the original Palm calendar program handled single vs. repeating events; it seemed to be able to handle just about anything you could throw at it in terms of event schedules; much more luck that I've had with iCalendar / vCalendar / hCalendar. | |
| Feb 23, 2011 at 1:21 | comment | added | Joe | When you're modeling the data, don't look at what the input format is -- ask what questions you want to be able to ask of the data. Without knowing what sort of questions you'll have, we can't figure out the queries that we'd need to run against the data structures, and so if it was a good design or not. | |
| Feb 23, 2011 at 0:29 | answer | added | BillThor | timeline score: 1 | |
| Feb 22, 2011 at 23:12 | history | asked | Vicsig | CC BY-SA 2.5 |