Don't force _id to be ObjectId about mongojs HOT 5 CLOSED

Yes - mongojs currently casts all _id properties as ObjectIds.

I'm willing to change this to support the use-case you describe and expose a explicit ObjectId wrapper or something if you want to use that.

from mongojs.

That's certainly something I'd use if it was changed. The workaround is to maintain a separate id field in each model and replace any .save() calls with .update({id:object.id}, object, {upsert:true}) which works but is a lot more complex than it could be.

Thanks very much for mongojs. I really appreciate the effort to stick with the shell API

On Sep 22, 2011, at 6:16 AM, Mathias [email protected] wrote:

Yes - mongojs currently casts all _id properties as ObjectIds.

I'm willing to change this to support the use-case you describe and expose a explicit ObjectId wrapper or something if you want to use that.

Reply to this email directly or view it on GitHub:
#5 (comment)

from mongojs.

Should be fixed in f703899. Let me know if it works.

from mongojs.

It works perfectly, thank you very much!

from mongojs.

This is indeed fixed, thank you very much!

On Fri, Sep 23, 2011 at 3:59 AM, Mathias Buus <
[email protected]>wrote:

Should be fixed in f703899.
Let me know if it works.

Reply to this email directly or view it on GitHub:
#5 (comment)

from mongojs.