-
Notifications
You must be signed in to change notification settings - Fork 163
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
non unique indexes for paranoid docs #183
non unique indexes for paranoid docs #183
Conversation
+1 |
Thanks! This is very interesting. I am wondering if it would be better to factor out the index creation into a concern so that people that use the old index format can still upgrade to new versions without recreating indexes. Thought or ideas on better solutions? |
Bunp @tomdmaguire, care to answer @digitalplaywright's question above? Thanks! |
FYI MongoDB 3.2 will support partial indexes which will make for a better solution here--you can declare unique as long as http://docs.mongodb.org/manual/release-notes/3.1-dev-series/ |
@johnnyshields @tomdmaguire After merging #172 (via #227) I read everything there's to read here and there and I don't understand what the problem is with paranoid documents and the slug index. Can someone explain it to me like a 2 yo and tell me what we should do with this PR? Thanks. |
|
Okay this is a very clear explanation! So I think this particular PR can be closed, because it's fully addressed in #227 which effectively "fixes" the scenario that was attempted here by introducing a sparse index? And the specs now create database-level indexes so we should be good. |
Does paranoid doc remove the value for |
fixes paranoid issue described in #172 (updated for latest version of code)