You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Edge labels are case sensitive for the most part. However when OrientDB adds edge classes it does it in a case insensitive way. Therefore if two objects in the model have two separate adjacencies where the label of one is the same as the label of the other but with different capitalization it causes unexpected behavior.
The way this presented to me is that the "loot" label/class was registered first, so anytime i try to create edges with the "Loot" label it would appear to succeed but the label created would actually be "loot" (lowercase). This resulted in any lookups based on edge labels to fail since those were still case sensitive.
The text was updated successfully, but these errors were encountered:
Edge labels are case sensitive for the most part. However when OrientDB adds edge classes it does it in a case insensitive way. Therefore if two objects in the model have two separate adjacencies where the label of one is the same as the label of the other but with different capitalization it causes unexpected behavior.
The way this presented to me is that the "loot" label/class was registered first, so anytime i try to create edges with the "Loot" label it would appear to succeed but the label created would actually be "loot" (lowercase). This resulted in any lookups based on edge labels to fail since those were still case sensitive.
The text was updated successfully, but these errors were encountered: