Host: ObjectID('AAAB') // Reference to the Host document
Suitable for one-to-squillions, such as log messages. In mongoid you will write your scheme like this: class Student Check out the link I gave you and ask any thing. What Mongoid and MongoMapper do is to provide you with convenient methods to set up relations quite easily. Basically, in a NoSQL database it is up to you to decide how to organise the data and its relations, if there are any.
You can have any kind of document – with any kind of data – in a single collection. Documents are grouped inside Collections. In a NoSQL database like MongoDB there are not 'tables' but collections. You may be interested in using a ORM like Mongoid or MongoMapper. You should model your database appropriate to the data you store and the queries you intend to run. In fact, if you take a look at that link, it has a similar example. In addition, MongoDB has a DBRef standard that helps standardize the creation of these references. However, the database does contain the correct information. The database does not apply any constraints to the system ( i.e.: foreign key constraints), so there are no "cascading deletes" or "cascading updates". MongoDB uses collections instead of tables.Ĭlearly Jane's course list points to some specific courses. How to design table like this in mongodb?įirst, to clarify some naming conventions.
0 kommentar(er)
