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

Database/collection relationship is forgeable #3

Closed
alevy opened this issue Jan 20, 2012 · 2 comments
Closed

Database/collection relationship is forgeable #3

alevy opened this issue Jan 20, 2012 · 2 comments
Assignees

Comments

@alevy
Copy link
Member

alevy commented Jan 20, 2012

In the structured branch, accessP will happily accept and run a query on any database regardless of whether the policy was written by that database's owner or not. Database should be a field of Policy rather than a parameter to accessP

@ghost ghost assigned alevy Jan 20, 2012
@deian
Copy link
Member

deian commented Jan 22, 2012

As we discussed (writing this solely for record), we can address this by fusing the DB and Collection into a DBCollection which will be used by all primitives.

@deian
Copy link
Member

deian commented Jan 25, 2012

fixed in 9855469

@deian deian closed this as completed Jan 25, 2012
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