You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Language-Team: Chinese (http://www.transifex.com/projects/p/mongodb-manual/language/zh/)\n"
14
14
"MIME-Version: 1.0\n"
15
15
"Content-Type: text/plain; charset=UTF-8\n"
@@ -20,209 +20,161 @@ msgstr ""
20
20
# 0d8c0aebe92f473789375958ab691ee0
21
21
#:../source/core/index-single.txt:3
22
22
msgid"Single Field Indexes"
23
-
msgstr""
23
+
msgstr"单键索引"
24
24
25
25
# e13aa85b66194135861dc6b3ff21c7b8
26
26
#:../source/core/index-single.txt:7
27
-
msgid""
28
-
"MongoDB provides complete support for indexes on any field in a "
29
-
":term:`collection` of :term:`documents <document>`. By default, all "
30
-
"collections have an index on the :ref:`_id field <index-type-id>`, and "
31
-
"applications and users may add additional indexes to support important "
32
-
"queries and operations."
33
-
msgstr""
27
+
msgid"MongoDB provides complete support for indexes on any field in a :term:`collection` of :term:`documents <document>`. By default, all collections have an index on the :ref:`_id field <index-type-id>`, and applications and users may add additional indexes to support important queries and operations."
"MongoDB supports indexes that contain either a single field *or* multiple "
39
-
"fields depending on the operations that this index-type supports. This "
40
-
"document describes indexes that contain a single field. Consider the "
41
-
"following illustration of a single field index."
42
-
msgstr""
32
+
msgid"MongoDB supports indexes that contain either a single field *or* multiple fields depending on the operations that this index-type supports. This document describes indexes that contain a single field. Consider the following illustration of a single field index."
":doc:`/core/index-compound` for information about indexes that include "
48
-
"multiple fields, and :doc:`/core/indexes-introduction` for a higher level "
49
-
"introduction to indexing in MongoDB."
50
-
msgstr""
37
+
msgid":doc:`/core/index-compound` for information about indexes that include multiple fields, and :doc:`/core/indexes-introduction` for a higher level introduction to indexing in MongoDB."
msgid"Given the following document in the ``friends`` collection:"
60
-
msgstr""
48
+
msgstr"假设在 ``friends`` 集合有如下稳定："
61
49
62
50
# 8e31e608721e474cac80745a160db4e8
63
51
#:../source/core/index-single.txt:36
64
52
msgid"The following command creates an index on the ``name`` field:"
65
-
msgstr""
53
+
msgstr"以下命令将会在 ``name`` 键上建立一个索引："
66
54
67
55
# 0907c4a7358544c89ecaf2283d502998
68
56
#:../source/core/index-single.txt:43
69
57
msgid"Cases"
70
-
msgstr""
58
+
msgstr"案例"
71
59
72
60
# 9efe58a785a94750883ca945cf62d964
73
61
#:../source/core/index-single.txt:52
74
62
msgid"``_id`` Field Index"
75
-
msgstr""
63
+
msgstr"``_id`` 键上的索引"
76
64
77
65
# acf404cf51204c4cbdc9205132fd09e0
78
66
#:../source/core/index-single.txt:54
79
-
msgid""
80
-
"MongoDB creates the ``_id`` index, which is an ascending :ref:`unique index "
81
-
"<index-type-unique>` on the ``_id`` field, for all collections when the "
82
-
"collection is created. You cannot remove the index on the ``_id`` field."
83
-
msgstr""
67
+
msgid"MongoDB creates the ``_id`` index, which is an ascending :ref:`unique index <index-type-unique>` on the ``_id`` field, for all collections when the collection is created. You cannot remove the index on the ``_id`` field."
"Think of the ``_id`` field as the :term:`primary key` for a collection. "
89
-
"Every document *must* have a unique ``_id`` field. You may store any unique "
90
-
"value in the ``_id`` field. The default value of ``_id`` is an "
91
-
":term:`ObjectId` which is generated when the client inserts the document. An"
92
-
" :term:`ObjectId` is a 12-byte unique identifier suitable for use as the "
93
-
"value of an ``_id`` field."
94
-
msgstr""
72
+
msgid"Think of the ``_id`` field as the :term:`primary key` for a collection. Every document *must* have a unique ``_id`` field. You may store any unique value in the ``_id`` field. The default value of ``_id`` is an :term:`ObjectId` which is generated when the client inserts the document. An :term:`ObjectId` is a 12-byte unique identifier suitable for use as the value of an ``_id`` field."
"In :term:`sharded clusters <sharded cluster>`, if you do *not* use the "
100
-
"``_id`` field as the :term:`shard key`, then your application **must** "
101
-
"ensure the uniqueness of the values in the ``_id`` field to prevent errors."
102
-
" This is most-often done by using a standard auto-generated "
103
-
":term:`ObjectId`."
104
-
msgstr""
77
+
msgid"In :term:`sharded clusters <sharded cluster>`, if you do *not* use the ``_id`` field as the :term:`shard key`, then your application **must** ensure the uniqueness of the values in the ``_id`` field to prevent errors. This is most-often done by using a standard auto-generated :term:`ObjectId`."
"Before version 2.2, :term:`capped collections <capped collection>` did not "
110
-
"have an ``_id`` field. In version 2.2 and newer, capped collections do have "
111
-
"an ``_id`` field, except those in the ``local`` :term:`database`. See "
112
-
":ref:`Capped Collections Recommendations and Restrictions <capped-"
113
-
"collections-recommendations-and-restrictions>` for more information."
114
-
msgstr""
82
+
msgid"Before version 2.2, :term:`capped collections <capped collection>` did not have an ``_id`` field. In version 2.2 and newer, capped collections do have an ``_id`` field, except those in the ``local`` :term:`database`. See :ref:`Capped Collections Recommendations and Restrictions <capped-collections-recommendations-and-restrictions>` for more information."
"You can create indexes on fields embedded in sub-documents, just as you can "
125
-
"index top-level fields in documents. Indexes on embedded fields differ from "
126
-
":ref:`indexes on sub-documents <index-sub-documents>`, which include the "
127
-
"full content up to the maximum :limit:`index size <Index Key>` of the sub-"
128
-
"document in the index. Instead, indexes on embedded fields allow you to use "
129
-
"a \"dot notation,\" to introspect into sub-documents."
130
-
msgstr""
92
+
msgid"You can create indexes on fields embedded in sub-documents, just as you can index top-level fields in documents. Indexes on embedded fields differ from :ref:`indexes on sub-documents <index-sub-documents>`, which include the full content up to the maximum :limit:`index size <Index Key>` of the sub-document in the index. Instead, indexes on embedded fields allow you to use a \"dot notation,\" to introspect into sub-documents."
"The ``metro`` field is a subdocument, containing the embedded fields "
167
-
"``city`` and ``state``. The following command creates an index on the "
168
-
"``metro`` field as a whole:"
169
-
msgstr""
122
+
msgid"The ``metro`` field is a subdocument, containing the embedded fields ``city`` and ``state``. The following command creates an index on the ``metro`` field as a whole:"
msgid"The following query can use the index on the ``metro`` field:"
174
-
msgstr""
128
+
msgstr"如下查询可以利用到基于 ``metro`` 键的索引："
175
129
176
130
# d871c326bce44300923a4ed117f017c0
177
131
#:../source/core/index-single.txt:159
178
-
msgid""
179
-
"This query returns the above document. When performing equality matches on "
180
-
"subdocuments, field order matters and the subdocuments must match exactly. "
181
-
"For example, the following query does not match the above document:"
182
-
msgstr""
132
+
msgid"This query returns the above document. When performing equality matches on subdocuments, field order matters and the subdocuments must match exactly. For example, the following query does not match the above document:"
0 commit comments