Timeline for How can one think of a relational schema in terms of storing it in a NoSQL database?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 29, 2016 at 20:29 | comment | added | GHP | If every entity, or the majority of all the entities, need to be related in many-to-many that way, then you could just store each type (Song, Album, Artist, Band, etc) as a separate top-level document, with IDs and crucial denormalized fields in each for the relationships. At that point you MIGHT start watering down the benefits of a document database though, as opposed to using a relational database. Doc Databases still give you lots of benefits (scalability, fast reads, better full-text searching) if you are willing to enforce their weak referential integrity in the app level. | |
| Apr 29, 2016 at 20:22 | history | edited | GHP | CC BY-SA 3.0 |
added 89 characters in body
|
| Apr 29, 2016 at 20:08 | comment | added | JeffO | What if there's more than one band on an album? Seems more of a many to many relationships | |
| Apr 29, 2016 at 17:59 | history | answered | GHP | CC BY-SA 3.0 |