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

collection.database should be a Database, not a Collection #283

Closed
alanbriolat opened this issue Dec 13, 2016 · 2 comments
Closed

collection.database should be a Database, not a Collection #283

alanbriolat opened this issue Dec 13, 2016 · 2 comments

Comments

@alanbriolat
Copy link

In writing some tests for a database migration layer that interacts with MongoEngine, I've found that the database attribute on mongomock's Collection follows the "sub-collection" behaviour rather than exposing the Database object. It seems like what I really want is stored as the _database attribute on mongomock's Collection.

Expected behaviour is documented here.
@pcorpet
Copy link
Member

pcorpet commented Mar 6, 2017

I ran in the same issue and suggested #304

@pcorpet
Copy link
Member

pcorpet commented Aug 29, 2018

#304 was merged and fixes this.

@pcorpet pcorpet closed this as completed Aug 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alanbriolat @pcorpet