Handling Documents that do not have ObjectID about mongodb-rest HOT 2 CLOSED

+1 to mgd216,
Here it is assumed that the _id would be always going to be of BSON type ObjectID, which is false assumption. The assumption is made at following links, and other places as well.

• https://github.com/tdegrunt/mongodb-rest/blob/master/lib/rest.js#L23
• https://github.com/tdegrunt/mongodb-rest/blob/master/lib/rest.js#L91
• https://github.com/tdegrunt/mongodb-rest/blob/master/lib/rest.js#L109

Guess, one should be able to dictate using config.js ( or mongodb-rest should be able to do a smart guess) as what is the BSON type for _id field. E.g when it comes to uuid as values for _id, the BSON Binary type with subtype as UUID should be used ( See http://bsonspec.org/#/specification )

Also, node-mongodb-native already provide the support for various types. See https://github.com/christkv/node-mongodb-native/blob/master/examples/types.js#L30 and https://github.com/christkv/node-mongodb-native/blob/master/external-libs/bson/binary.cc#L21.

Please, also see the discussion regarding this issue at http://groups.google.com/group/node-mongodb-native/browse_thread/thread/73e0a02b5dd08102.

@mgd216, any specific reason why you don't want to store UUIDs as BSON Binary type with subtype UUID ? Why you have choose BSON type string to store them, it will occupy twice the space that too with indexing overhead.

from mongodb-rest.

Also, at https://github.com/tdegrunt/mongodb-rest/blob/master/lib/rest.js#L74 assuming that the _id would have equivalent hex string is not helpful for anybody who is dealing with BSON types other than ObjectIds.

from mongodb-rest.