-
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
Improve identity handling and allow custom id generation #344
Labels
Comments
nmervaillie
added a commit
that referenced
this issue
Mar 28, 2017
…ew annotations @id and @generated). #344.
nmervaillie
added a commit
that referenced
this issue
Apr 12, 2017
Reduce coupling on native long IDs in the mapping context
nmervaillie
added a commit
that referenced
this issue
Apr 20, 2017
Reduce coupling on native long IDs in the mapping context Add javadoc Introduce wrapping entities with holder containing native graph id
nmervaillie
added a commit
to nmervaillie/neo4j-ogm
that referenced
this issue
May 31, 2017
Add test for @id inheritance support
nmervaillie
added a commit
to nmervaillie/neo4j-ogm
that referenced
this issue
May 31, 2017
Use Object type as node identifiers instead of Longs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
All objects must define the internal Neo4j ID, either using the
Long id
semantic in their models or annotating it with @GraphID. This id must always be long and must never be set by the user. In fact it should probably not be exposed at all in this manner at all as it has led to a lot of confusion and misunderstanding. This is further compounded in SDN where repositories allow users to define their own ID’s and then provide several support methods around querying, saving, deleting etc. SD Repositories intend to allow developers to define their own Ids including their types.To be clear, it’s fine that the Long id can be used as an ID but it shouldn’t be the only mechanism and certainly not always tied to being a Long in the context of an ID.
The text was updated successfully, but these errors were encountered: