DB documents with integer fields silently dropped about meteor HOT 5 CLOSED

I am using integer fields successfully in two meteor projects right now, I haven't noticed anything getting dropped. Specifically, I'm using integers to maintain the order in a couple collections.

slides.meteor.com
touring.meteor.com

from meteor.

BSON has integer and number/double ("double precision floating-point format in JavaScript, generally depends on implementation"), maybe the difference comes from there? From the NOTEs file:

"Only the basic JSON types are implemented (string, number, boolean, null, array, object)."

and

"we don't support the integer type yet"

If that helps, it's an int() added to the DB by a Python script (pymongo) that caused the problem for me.

from meteor.

Interesting, my mistake, I'm probably just using numbers that look like integers.

from meteor.

Would be nice to output a warning if possible (which is why I'm marking this as "unconfirmed-bug").

Also, touching upon this somewhere in http://docs.meteor.com/ would be helpful.

from meteor.

Numbers in general do work in Meteor. There might be a more specific issue here (conversion to some special Mongo type? the "length" name being strange?). If you have a specific reproduction recipe (see https://github.com/meteor/meteor/wiki#wiki-bugs ) please re-open.

from meteor.