Timeline for Database architecture with extension in mind
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| 10 hours ago | vote | accept | ncmprbl | ||
| Dec 7 at 22:58 | answer | added | Michael Green | timeline score: 0 | |
| Dec 6 at 9:26 | comment | added | Vérace | With respect to the JSON - PostgreSQL has a JSONB type (plus a plain JSON - more or less deprecated now) that you could use to "pick-n-mix" your model - its performance compares favourably to MongoDB - see here and here - although, the authors say you should perform your own benchmarks - but at least they have been "honest and transparent" - 50 pages of a .pdf and loads of github stuff - data/results! À vous le choix! | |
| Dec 5 at 22:17 | comment | added | ncmprbl | @Vérace, ah, it's not too many games - we're just talking about hypothetical numbers in case there was an actual extension. But thank you for your reply on the topic! | |
| Dec 5 at 19:15 | comment | added | Vérace | Hi, and welcome to dba.se! How many games/sports will you be looking at? I don't see any problem with having a table for each sport/game - they all have different rules so your backend (and frontend) will have have to treat them differently anyway! The data entry screens will be different... &c. | |
| Dec 5 at 19:04 | answer | added | Shahram | timeline score: 1 | |
| S Dec 5 at 17:57 | review | First questions | |||
| Dec 5 at 18:27 | |||||
| S Dec 5 at 17:57 | history | asked | ncmprbl | CC BY-SA 4.0 |