Skip to content
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

Newly created edges are (sometimes) not recognized #3

Open
freemo opened this issue Sep 18, 2017 · 0 comments
Open

Newly created edges are (sometimes) not recognized #3

freemo opened this issue Sep 18, 2017 · 0 comments
Labels

Comments

@freemo
Copy link
Member

freemo commented Sep 18, 2017

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.

@freemo freemo added the bug label Sep 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant