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

Support single @Id field which may be any unique sortable value (e.g. ObjectId) #93

Open
nealeu opened this issue Sep 25, 2012 · 0 comments

Comments

@nealeu
Copy link
Member

nealeu commented Sep 25, 2012

Currently our AbstractMappingFuzzyRepository implementation expects @id to be a String representation of the internal fuzzydb Ref.

Ref should only be used if explicitly specified, and the preferred external support should be @id based on UUID or BSON ObjectId (which is more compact).

The mapping layer should be refactored to allow any @id field to be used, to create an index on that field (using DataOperations.ensureIndex() ), and for findOne() to look up from that index to get the internal reference for the object with which to then do update, delete operations.

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

1 participant