This repository was archived by the owner on Aug 25, 2020. It is now read-only.
Add support for custom primary keys #44
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When switching to a UUID the find_one method will fail unless you pass a
hash: `{ :_id => id }`
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is probably seems like it's coming out of left field... We have integrated
rack-oauth2-serverinto our API and the rest of our API usesUUIDforidfields and we wanted to ensure consistency. Forking and modifying the codebase was the best option we could find (would have required too much monkey patching).The idea here is you can swap out
BSON::ObjectIdfor aUUIDlike so:Let us know if this is something you are interested in and if there are changes/improvements we can make.