[DOCS-116] bsonspec.org should make it more clear which byte strings allow null bytes Created: 25/Jan/12 Updated: 27/Jul/16 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | bsonspec |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Trivial - P5 |
| Reporter: | Aaron Staple | Assignee: | Kay Kim (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 7 years, 29 weeks ago |
| Description |
|
In particular, null bytes are allowed in string typed values but not in field names. In order to see that this is the case I need to put my mouse on the word "CString" and read the info popup. If it were up to me, I'd specify this property as part of the grammar itself. Not sure if bsonspec.org falls under the jira Documentation project - if not, sorry for the spam. |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed for housekeeping on 7/27/2016 by Emily Hall. |
| Comment by Sam Kleinman (Inactive) [ 08/Feb/12 ] |
|
Seems straightforward/legitimate, but I think you (Kyle) know how best to handle/process. |