-
Notifications
You must be signed in to change notification settings - Fork 493
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
Fixes #302 - procedure to rename property, rename label, rename reltype #371
Conversation
}); | ||
} | ||
if (prop != null) { | ||
Iterable<ConstraintDefinition> constraintsForProps = db.schema().getConstraints(); |
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.
indexes too
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.
right
}); | ||
}); | ||
} | ||
List<BatchAndTotalResult>targetLongList = iterate.collect(Collectors.toList()); |
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.
iterate.findFirst().orElse(null);
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.
better
Looks good to me. |
can you fix the two small things? |
@jexp ok to postpone manual and automatic indexes management? |
@inserpio sure, we can even leave it to the user or make it an option |
… rename reltype
… rename reltype (neo4j-contrib#371)
Indexes and constraints are managed, legacy indexes are not