{"push_id":720417492,"size":1,"distinct_size":1,"ref":"refs/heads/2.3-mpc-for-relationships-kernel","head":"f54414a22c9b7ec4492df3a4d6b5cc6de72b1c60","before":"dcec24d2d947fecdaf4197f813dafb61039378a7","commits":[{"sha":"f54414a22c9b7ec4492df3a4d6b5cc6de72b1c60","author":{"email":"fc76649b9d8bbdfbffafcf110b227f804bfc8076@neotechnology.com","name":"lutovich"},"message":"Introduced notion of relationship constraints\n\nThis commit is mostly about renaming and refactoring of class hierarchies\nthat are used to represent indexes and constraints.\n\nFollowing changes were made:\n\n - MandatoryPropertyConstraint renamed to MandatoryNodePropertyConstraint\n    together with all relevant methods\n\n - reworked hierarchy of PropertyConstraint class to reflect\n    existence of node and relationship constraints\n\n - reworked hierarchy of SchemaRule and it's interface to\n    provide information about both label and relationship type.\n    This is expected to be a temporary state of the interface until\n    it is further refactored and specialized\n\n - reworked hierarchy of ConstraintDefinition interface which\n    now also has accessor methods for both label and relationship type.\n    This is expected to be a temporary state, which can't be really fixed\n    until next major release","distinct":true,"url":"https://api.github.com/repos/lutovich/neo4j/commits/f54414a22c9b7ec4492df3a4d6b5cc6de72b1c60"}]}