No id returned by insert callback about ground-db HOT 4 CLOSED

._id has been a problem with groundDB so far. See #27

I work around it by including _id in the object passed to Collection.insert() using collection2 and including an autovalue for _id using Random.id()

from ground-db.

Thanks @scottburch, that workaround did the trick for me.

For others, to make it work with CFS, you need to upload a FS.File. Do the following:

Template.test.events
  'change input' : (e) ->
    file = new FS.File e.currentTarget.files[0]
    file._id = Random.id()
    uploadedFile = col.insert file
    console.log 'uploaded', uploadedFile._id # zt7JbYQjWwKNqtFEu

from ground-db.

Thanks guys!
Strange - I'd like to get to the bottom of this issue - ground:db is using a normal Meteor.collection - I can see that _id is missing from the method call it self though in the qa test - I'll have a closer look at this.

from ground-db.

This is still an odd issue, I'm trying to track down the true issue... Its not consistent, and the workaround should not be necessary..

I can replicate the issue in my qa test clients - but if I open the console and do db.insert({ foo: 'test' }, function(err, id) { console.log(id); }); it returns an id...

Also I can replicate this issue using a regular Meteor.Collection... In fact at the moment grounddb is using plain Meteor.Collection for this - So somethings weird is going on...

What I can see is that the Meteor.Collection.insert is not adding an _id in the data sent to Meteor.apply.

from ground-db.