Skip to content

[Feature Request] Support neo4j constraints #14641

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.

Sign up for GitHub

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

Jump to bottom
Open
mburak opened this issue Oct 29, 2015 · 1 comment
Open

[Feature Request] Support neo4j constraints #14641

mburak opened this issue Oct 29, 2015 · 1 comment
Labels
relates-to: grails-data-neo4j

Comments

@mburak
Copy link

mburak commented Oct 29, 2015

GORM constraints should create constraints on the neo4j side.

Below you can find some documentation:
http://neo4j.com/docs/stable/query-constraints.html

And also you can find some documentation about new neo4j 2.3 Property Existence Constraints:
http://neo4j.com/blog/neo4j-2-3-enterprise-applications-at-scale/
@graemerocher
Copy link
Contributor

Partially implemented by apache/grails-data-mapping@dc072a9

Although not with support for null constraints yet (only unique)

@graemerocher graemerocher added this to the milestone Sep 14, 2016
@graemerocher graemerocher modified the milestone: Mar 3, 2017
jamesfredley referenced this issue in apache/grails-data-mapping Mar 8, 2025
@puneetbehl
Merge pull request #568 from grails/renovate/gorm-datastore-monorepo
6b61f1b 
Update gorm-datastore monorepo to v8.0.2
@jdaugherty jdaugherty transferred this issue from apache/grails-data-mapping Apr 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
relates-to: grails-data-neo4j
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@graemerocher @mburak @jdaugherty