-
Notifications
You must be signed in to change notification settings - Fork 56
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
Feature: change @Id to save _key instead of _id #78
Comments
Hi, Will this also be added to the 1.x.x branch? (I haven't upgraded spring data yet) |
Hi @sigh-man, because this is a breaking change we have only planned to provide this with the upcoming major release 3.0.0. |
OK - Thanks. I assume the arango-spring-data 3 will require spring-data 2 ? - I guess I'll just have to get on with upgrading spring ... (been meaning to anyway) |
Yes, arangodb-spring-data 3 will require spring-data 2 |
Implementation done. Feature will be included in the upcoming 3.0.0 release |
Currently a field annotated with
@Id
is saved as_id
in ArangoDB. Since this field is more for internal usage and does not offer any benefit to the user, we should change@Id
to represent the document field_key
instead, like@Key
currently does. This eliminates the need of having two fields (for@Id
and@Key
) when using user generated keys.The text was updated successfully, but these errors were encountered: