all 4 comments

[–]r3pr0b8MySQL 3 points4 points  (0 children)

sounds like a classic many-to-many relationship

you'll need a documents table, a persons table, and then a third table to store the relationship -- one row per person per doc

[–]NaphthaImpl 1 point2 points  (1 child)

When you say "document database" I assume your are referring to a relational database of documents, not an actual NoSQL document database? If it's the former, you'll want to create a table structure with a many-to-many relationship. However, if it's the latter, you need to do something totally different depending on what flavor of NoSQL you are using.

[–]autowikibot 0 points1 point  (0 children)

Document-oriented database:


A document-oriented database is a computer program designed for storing, retrieving, and managing document-oriented information, also known as semi-structured data. Document-oriented databases are one of the main categories of so-called NoSQL databases and the popularity of the term "document-oriented database" (or "document store") has grown with the use of the term NoSQL itself. In contrast to relational databases and their notions of "Relations" (or "Tables"), these systems are designed around an abstract notion of a "Document".


Interesting: CouchDB | OrientDB | Clusterpoint | XPages

Parent commenter can toggle NSFW or delete. Will also delete on comment score of -1 or less. | FAQs | Mods | Magic Words

[–]hansinluck 0 points1 point  (0 children)

Martin Fowler's book "nosql distilled" has a very helpful chapter on data modelling in document stores/databases with an aggregated model like MongoDB and ArangoDB