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

integrate with mongo db 3.2 document validation #312

Open
SierraGolf opened this issue Mar 13, 2016 · 2 comments
Open

integrate with mongo db 3.2 document validation #312

SierraGolf opened this issue Mar 13, 2016 · 2 comments

Comments

@SierraGolf
Copy link

since mongo db 3.2 there is database level support for validations. is there anything on the roadmap towards integrating with that functionality?

I guess this could also be a good approach for solving #12.

@mtchllbrrn
Copy link

I'm also curious about this. +1

@StorytellerCZ
Copy link
Member

So looking at the docs, I'm thinking that we have two options here. Either we provide a new way how to make collections which when provided schema will implement it to MongoDB as well, or while attaching schema we could add a new option that when true will add it to MongoDB. We can do both, but I think the second option is better as it follows the current workflow.
Either way we will now have to look over the differences in schemas and how to bridge them.
From my point of view enabling MongoDB validation the use case would be if you have other apps connecting to your DB and you want to enforce rules across the board. If you have just Meteor app then you won't need it (as it would be redundant to collection2 & simpl-schema), potentially we could utilize some functionality that is in MongoDB validation that is not in simpl-schema.

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

No branches or pull requests

4 participants