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

Document rollback when insert directly in Mongo CLI #73

Closed
firdausramlan opened this issue Nov 29, 2014 · 7 comments
Closed

Document rollback when insert directly in Mongo CLI #73

firdausramlan opened this issue Nov 29, 2014 · 7 comments

Comments

@firdausramlan
Copy link

When inserting first data directly in Mongo CLI for the first time, the view get updated with new data.

db.parties.insert({name: 'Party Name', description: 'Party Desc'});

But after inserting second data using Mongo CLI or browser, the first data just gone.

I'm testing the socially-step04

@Urigo
Copy link
Owner

Urigo commented Nov 30, 2014

Have you defined the parties collection first?

@firdausramlan
Copy link
Author

@paulvanbladel
Copy link

Yep. I confirm this behavior.
When adding records via the browser F-12 tools, works as expected, but directly in meteor mongo it fails as described above.

@paulvanbladel
Copy link

Unfortunately, for me, this issue lowers trust in the whole meteor - angular integration since data loss occurs.
Using a different front-end framework (angular in casu) should not change the back-end behavior and definitely not result in data loss.

@Urigo
Copy link
Owner

Urigo commented Dec 22, 2014

Sorry for not getting into that yet..
When you refresh the page, does the data returns or still only one left?

@Urigo Urigo closed this as completed in 528ae3b Dec 22, 2014
@Urigo
Copy link
Owner

Urigo commented Dec 22, 2014

@firdausramlan @paulvanbladel I worked on it today and found the problem!
Thank you so much for pointing that problem.
When we compare ID's, the structure of a new local Mongo object is different and the ID is in a different place.
I've tested it and the commit closed the issue automatically but please test it yourself with the new version:
https://github.com/Urigo/angular-meteor/releases/tag/0.5.11

@paulvanbladel
Copy link

Wow, many thanks for the update and solution.
cheers
paul.

kamilkisiela pushed a commit to kamilkisiela/angular-meteor that referenced this issue Sep 19, 2016
chore(git): Add gitingnore and git commit message validation
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

3 participants