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.

Sign up for GitHub

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

Jump to bottom

The two database implementations handle documents in mark-methods differently #336

Open
laserval opened this issue Jun 4, 2014 · 0 comments
Open

The two database implementations handle documents in mark-methods differently #336

laserval opened this issue Jun 4, 2014 · 0 comments
Assignees
@laserval
Labels
bug database test

Comments

@laserval
Copy link
Contributor

laserval commented Jun 4, 2014

For mongoDB, the document sent to markProcessed will get all its changes saved along with being marked as processed or other states.

For memoryDB, this is not true, and only the state will change.

This primarily means it is difficult to trust the tests since change may cause different behaviour in mongo and memory.
@laserval laserval self-assigned this Jun 5, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@laserval laserval

Labels
bug database test
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@laserval