-
Notifications
You must be signed in to change notification settings - Fork 973
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
feat: drop node target's key constraint requirement #2068
base: main
Are you sure you want to change the base?
feat: drop node target's key constraint requirement #2068
Conversation
This blocks Community Edition (CE) users, as the only way to emulate key constraints is to combine unique constraints (available in CE) with existence constraints (available only in Enterprise Edition).
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2068 +/- ##
============================================
- Coverage 46.16% 46.14% -0.02%
+ Complexity 3843 3835 -8
============================================
Files 856 855 -1
Lines 51010 50996 -14
Branches 5365 5363 -2
============================================
- Hits 23548 23532 -16
- Misses 25760 25762 +2
Partials 1702 1702
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Are the tests failures related to this change?
The test failures are all about the Neo4j container timing out:
One occurrence of this is:
Maybe a temporary issue on the CI side? |
This blocks Community Edition (CE) users, as the only way to emulate key constraints is to combine unique constraints (available in CE) with existence constraints (available only in Enterprise Edition).