Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
shilman80 opened this issue Oct 23, 2014 · 3 comments

Comments

@shilman80
Copy link

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.

@richsilv
Copy link
Owner

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
#2.

@richsilv
Copy link
Owner

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
#2.

@richsilv
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants