[DOCS-4491] Change field name restrictions for dots (.) to be consistent with 2.8 tools behavior Created: 09/Dec/14  Updated: 10/Dec/14  Resolved: 10/Dec/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: v1.3.15, mongodb-3.0

Type: Improvement Priority: Major - P3
Reporter: Michael Paik Assignee: Allison Reinheimer Moore
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents TOOLS-376 mongofiles allows for an empty prefix Closed
documents TOOLS-466 mongoimport should error if field nam... Closed
documents SERVER-16162 NamespaceString is inconsistently val... Closed
Participants:
Days since reply: 9 years, 10 weeks ago

 Description   

http://docs.mongodb.org/v2.6/core/document/#field-names states that field names cannot contain dots; this is no longer true (dots refer to subdocuments). The new behavior is that field names:

a) cannot contain consecutive dots e.g. a..b
b) cannot contain leading dots e.g. .a
c) cannot contain trailing dots e.g. b.

not necessarily in that order of importance.



 Comments   
Comment by Allison Reinheimer Moore [ 10/Dec/14 ]

Dot-notation!

Generated at Thu Feb 08 07:48:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.