Closed mwahle closed 5 years ago
This scenario won't work at all and fail at the second query when there is an index on the <class, property key> pair. Without an index, this will fail because the constraint casts the property as an integer which gets compared to a string in the second node. This is expected behavior. If you want to print properties of different types but same keys, the constraint block needs some other property that has same data type everywhere.
For now I am closing this bug. Please let me know if you want to discuss any specific scenario in particular.
Property
x
, once a string, once an int. We search for the int and get an error back: