meteor-dumb-collections icon indicating copy to clipboard operation
meteor-dumb-collections copied to clipboard

Error: Meteor does not currently support objects other than ObjectID as ids

Open shilman80 opened this issue 10 years ago • 3 comments

After trying out dumb-collections in a bigger app and running into issues, I've implemented a stripped down reproduction of the error (see README for details):

https://github.com/shilman80/dumb-collections-spike/

I'm sure it's related to not using server methods, as in dumb-collections-demo. However, I do not want the client to be able to update the collection at all, so I just simulated a server process updating the collection in Mongo.

Your help is very much appreciated.

shilman80 avatar Oct 23 '14 17:10 shilman80

How did you populate the server database? If it was outside of Meteor (i.e. in Mongo shell or with mongorestore), then that could be an issue that I hadn't thought of. This is purely based on the error text.

I'll have a play in a bit to see if I can shed any further light.

On Thu, Oct 23, 2014 at 6:45 PM, shilman80 [email protected] wrote:

After trying out dumb-collections in a bigger app and running into issues, I've implemented a stripped down reproduction of the error (see README for details):

https://github.com/shilman80/dumb-collections-spike/

I'm sure it's related to not using server methods, as in dumb-collections-demo. However, I do not want the client to be able to update the collection at all, so I just simulated a server process updating the collection in Mongo.

Your help is very much appreciated.

— Reply to this email directly or view it on GitHub https://github.com/richsilv/meteor-dumb-collections/issues/2.

richsilv avatar Oct 23 '14 17:10 richsilv

Ignore that - I'm looking at your repo and I can see you're doing it on server startup. Apologies...

On Thu, Oct 23, 2014 at 6:50 PM, Richard Silverton < [email protected]> wrote:

How did you populate the server database? If it was outside of Meteor (i.e. in Mongo shell or with mongorestore), then that could be an issue that I hadn't thought of. This is purely based on the error text.

I'll have a play in a bit to see if I can shed any further light.

On Thu, Oct 23, 2014 at 6:45 PM, shilman80 [email protected] wrote:

After trying out dumb-collections in a bigger app and running into issues, I've implemented a stripped down reproduction of the error (see README for details):

https://github.com/shilman80/dumb-collections-spike/

I'm sure it's related to not using server methods, as in dumb-collections-demo. However, I do not want the client to be able to update the collection at all, so I just simulated a server process updating the collection in Mongo.

Your help is very much appreciated.

— Reply to this email directly or view it on GitHub https://github.com/richsilv/meteor-dumb-collections/issues/2.

richsilv avatar Oct 23 '14 17:10 richsilv

Thanks for the repo - I've just opened an issue on it so that we can discuss the details of that exact case there. If it uncovers a specific issue then I'll track it here.

richsilv avatar Oct 23 '14 21:10 richsilv