Home IT Linux Windows Database Network Programming Server Mobile  
  Home \ Database \ MongoDB relations, references, index query coverage     - Ubuntu 14.04 LTS compiler installation R Source Code (Linux)

- Oracle study notes view (Database)

- Kitematic how seamless and DockerFILE (Server)

- Talk about Java EE Learning (Programming)

- How to use Monit to deploy a server to monitor the system (Server)

- Linux installation is larger than 2TB (UEFI interface) hard disk solution (Linux)

- Redhat 5 prohibit IPv6 (Linux)

- grep regular expression (Linux)

- C language - Traverse pci device (Programming)

- Internal class broadcasting needs public and static (Programming)

- Under CentOS Linux automatic backup MySQL database daily (Database)

- Let you Fun Ubuntu desktop eleven weapon (Linux)

- Hadoop2.6.3 build clusters and the development of MapReduce WIN7 by Eclipse on Linux demo (Server)

- How to install Nginx on FreeBSD 10.2 as an Apache reverse proxy (Server)

- Piostat - Monitoring and Statistics Linux process (Linux)

- Let Git variety of colors and custom log format output (Linux)

- The ORA-01113 error is handled with BBED without archiving (Database)

- Linux signal and orphans, and zombie process (Programming)

- After installing minimize RHEL / CentOS 7 we need to do (Linux)

- Oracle archive log size than the size of the online journal of the much smaller (Database)

  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.

- Binary tree traversal algorithm summary (recursive and non-recursive) (Programming)
- IBM Data Studio to use ---- window displays all rows (Database)
- Unity Greeter Badges: the lost session icon back to the login screen Ubuntu (Linux)
- Laravel configuration PhpStorm + Xdebug + Chrome settings Debug Environment (Server)
- Java Concurrency - multiple threads of HelloWorld (Programming)
- How to install Git client in Ubuntu (Linux)
- Ubuntu install Vendetta Online 14.04 (Linux)
- Python is not C (Programming)
- File permissions under Linux (Linux)
- Fedora && Arch Linux - the most romantic thing to happen now (Linux)
- Linux operating system, the internal and external security overview (Linux)
- Customize the output format in Linux history (Linux)
- Java call by value and by reference (Programming)
- Some common Linux commands Study Notes (Linux)
- The security administrator network analysis tools SATAN Introduction under Linux (Linux)
- Linux server dual-card dual-IP and single-card dual-IP configuration method (ReHat / CentOS) (Server)
- Linux yum command Detailed (Linux)
- Android Service service applications and the phone SMS Listener Listener (Programming)
- Kubernetes cluster deployment (Server)
- IntelliJ IDEA run in Mac10.9 and JDK7 environment (Linux)
  CopyRight 2002-2016 newfreesoft.com, All Rights Reserved.