Many to many relationships and RavenDB models  RavenDB, RavenDB
in Action, EventsZilla Comments (1)  I've recently come across
this question in StackOverflow titled "Many to many design for
NoSql (RavenDB)", and I thought it is a really good case of a
very frequently asked question worth featuring here:  I have two
simple objects, 'user' and 'events'. A user can enter many
events and an event can be entered by many users - a standard
many to many relationship. I'm trying to get out of the
relational database mindset!  Here are the queries/actions that
I'd like to run against the database:    • Get me all the events
that a user has not entered   • Get me all the events that a
user has entered   • Update all the events (properties like
remaining spaces) very frequently (data polled from various
external data sources).   • Removing events when they've expired
The OP then lists 3 options of solving this:    1. A "relational
approach": Create a new object, that links user and events. For
example, a "booking" obje