Home IT Linux Windows Database Network Programming Server Mobile  
  Home \ Database \ MongoDB relations, references, index query coverage     - How to Install Node.js in CentOS 7 (Linux)

- How to install new fonts on Ubuntu 14.04 and 14.10 (Linux)

- Cool Android realization SVG animation (Programming)

- LinkedList Basic Usage (Programming)

- Enterprise Hadoop cluster architecture - DNS installation (Server)

- Linux ps command (Linux)

- Three kinds of implementation model of the Linux thread history (Programming)

- Close common port to protect server security (Linux)

- MySQL related statements (CRUD) (SQLyog software) (Database)

- Android official recommendation: DialogFragment create dialog (Programming)

- Run two MySQL service on one server (Database)

- How to manage start-up applications in Ubuntu (Linux)

- Ubuntu 14.10 / 14.04 / 12.04 installation GNOME Pie 0.5.6 (Linux)

- How to manage and use Logical Volume Management LVM in Ubuntu (Linux)

- Heartbeat cluster components Overview (Server)

- grep command Detailed and relevant examples (Linux)

- A brief introduction to some important Docker commands (Server)

- Node.js installed on Ubuntu Upstream version (Linux)

- Talking about the shortcomings and deficiencies of the firewall (Linux)

- Linux alpine use the command line to access Gmail (Linux)

  MongoDB relations, references, index query coverage
  Add Date : 2018-11-21      

First, the relationship


MongoDB representation interlinkages between multiple documents in logic. You can establish contact by embedding and references between documents. Relationship in MongoDB can be: 1 to 1,1 for more and more of the 1-many.

A user can use more than one address, which is typical of many relationship.

user documentation can be:

  "_id": ObjectId ( "52ffc33cd85242f436000001"),
  "name": "Tom Hanks",
  "contact": "987654321",
  "dob": "01-01-1991"

address document can be:

  "_id": ObjectId ( "52ffc4a5d85242602e000000"),
  "building": "22 A, Indiana Apt",
  "pincode": 123456 ,
  "city": "Los Angeles",
  "state": "California"

1, the embedded relationship

Using the embedded method, the address of the user's documents into the document

    "_id": ObjectId ( "52ffc33cd85242f436000001"),
  "contact": "987654321",
  "dob": "01- 01-1991 ",
 " name ":" Tom Benzamin ",
 " address ": [
        "building": "22 A, Indiana Apt",
        "pincode": 123456,
        "city": "Los Angeles",
        "state": "California"
        "building": "170 A, Acropolis Apt",
        "pincode": 456789,
        "city": "Chicago",
        "state": "Illinois"

If so, then you can save so get the user's address:

db.users.findOne ({ "name": "Tom Benzamin"}, { "address": 1})

The disadvantage of this data structure is that if users and address the increasing amount of data becomes larger and larger, will affect the read and write performance.

2, a reference approach

This method is similar to a relational database foreign key, will address the _id saved to user documentation

  "_id": ObjectId ( "52ffc33cd85242f436000001"),
  "contact": "987654321",
  "dob": "01-01- 1991 ",
 " name ":" Tom Benzamin ",
 " address_ids ": [
      ObjectId (" 52ffc4a5d85242602e000000 "),
      ObjectId ( "52ffc4a5d85242602e000001")

We can read the user's address object id (ObjectId) to get detailed information about the user's address. This method requires two queries, the first query object id user's address (ObjectId), the second address for more information on the user's query by id.

var result = db.users.findOne ({ "name": "Tom Benzamin"}, { "address_ids": 1})
var addresses = db.address.find ({ "_ id": { "$ in": result [ "address_ids"]}})

Second, the database references

mongodb There are two references: a reference manual (Manual References) and DBRefs

If we have a different set (address_home, address_office, address_mailing, etc.) stored in a different address (address, office address, mailing address, etc.). This time when we call different address, you need to specify a collection, a document reference document from multiple collections, we should use DBRefs.

DBRef form of:

{$ ref:, $ id:, $ db:  }

where $ ref: collection name, $ id: reference id, $ db: Database name (optional).

The following example uses a user data document DBRef, field address:

  "_id": ObjectId ( "53402597d852426020000002"),
  "address": {
  "$ ref": "address_home",
  "$ id": ObjectId ( "534009e4d852427820000002"),
  "$ db": "w3cschoolcc"},
  "contact": "987654321",
  "dob": "01-01-1991",
  "name": "Tom Benzamin"

address DBRef field specifies the address referenced documents are under address_home collection w3cschoolcc database, id is 534009e4d852427820000002.

The following code, we specify $ ref parameter (address_home set) to find the collection at the specified id user address information:

var user = db.users.findOne ({ "name": "Tom Benzamin"})
var dbRef = user.address
db [dbRef $ ref.] .findOne ({ "_ Id ": (. dbRef $ id)})

The above examples returns address_home collection address data:

  "_id": ObjectId ( "534009e4d852427820000002"),
  "building": "22 A, Indiana Apt",
  "pincode": 123456 ,
  "city": "Los Angeles",
  "state": "California"

Third, coverage index query

cover the following query is a query:
• all query fields are part of the index
• The query returns all the fields in the same index

Because all appear in the query field is part of the index, MongoDB data files without having to retrieve the entire match query terms and return query results using the same index. Because the index reside in RAM, the access to data than to read data much faster by scanning documents from the index.

Example: user set:


  "_id": ObjectId ( "53402597d852426020000002"),
  "contact": "987654321",
  "dob": "01-01- 1991 ",
 " gender ":" M ",
 " name ":" Tom Benzamin ",
 " user_name ":" tombenzamin "

Create joint index, gender and field user_name

db.users.ensureIndex ({gender: 1, user_name: 1})

Now, the index will cover the following query:

db.users.find ({gender: "M"}, {user_name: 1, _id: 0})

For the above query, MongoDB's not going to file for a database. Instead, it extracts the data from the index, which is very fast data query. Since our index does not include the _id field, _id will be returned by default in the query, we can concentrate exclude it in MongoDB query results. The following examples are not ruled _id, the query will not be overwritten:

db.users.find ({gender: "M"}, {user_name: 1})

If all of the index field is an array index query coverage can not be used, all index field is a sub-document.

- Linux installation skynet issue summary (Linux)
- Ubuntu 14.04 solved using MyEclipse 10.7 flash back (Linux)
- Oracle through the alarm log view and inspect the main library, physical and snapshot standby database (Database)
- Let you Fun Ubuntu desktop eleven weapon (Linux)
- Erlang concurrency and foundation (Programming)
- Linux redirection and piping (Linux)
- MySQL to manage multiple instances of method (Database)
- Math objects easily overlooked but very convenient method --JavaScript (Programming)
- Linux / proc directory Comments (Linux)
- Compile and install the latest version of Redis Stable (Database)
- Linux dmidecode command detail (Linux)
- Elaborate 10-point difference between the new and malloc (Programming)
- Linux crontab (Linux)
- How to modify the SQL Server auto-increment value and the corresponding solution (Database)
- Diagnose and resolve the SSH connection slow (Linux)
- Linux Network Programming - raw socket instance: MAC header message analysis (Programming)
- Single Instance ASM under CRS-4124, CRS-4000 error handling (Database)
- Nodejs command-line program development tutorial (Programming)
- According to the national position on how to block traffic in Linux (Server)
- Vi syntax highlighting settings (Linux)
  CopyRight 2002-2016 newfreesoft.com, All Rights Reserved.