Unexpected behavior for creation/query of kebab-case property keys. #7128

Closed
shooit opened this Issue Jan 27, 2017 · 5 comments

Comments

Projects
None yet
3 participants
@shooit

shooit commented Jan 27, 2017

OrientDB Version, operating system, or hardware.

  • v2.0 SNAPSHOT[ ] - .18[ ] .17[ ] .16[ ] .15[ ] .14[ ] .13[ ] .12[ ] .11[ ] .10[ ] .9[ ] .8[ ] .7[ ] .6[ ] .5[ ] .4[ ] .3[ ] .2[ ] .1[ ] .0[ ]
  • v2.1 SNAPSHOT[ ] - .16[ ] .15[ ] .14[ ] .13[ ] .12[ ] .11[ ] .10[ ] .9[ ] .8[ ] .7[ ] .6[ ] .5[ ] .4[ ] .3[ ] .2[ ] .1[ ] .0[ ]
  • v2.2 SNAPSHOT[ ] - .14[x]

Operating System

  • Linux
  • MacOSX
  • Windows
  • Other Unix
  • Other, name?

Expected behavior and actual behavior

Background: I am writing a Clojure wrapper for OrientDB. Clojure makes frequent use of kebab-case names.

I can create a vertex with a property in kebab-case
v1 = graph.addVertex(null, "string-key", "value")

But on query, the key must be escaped in backticks

graph.getVertices("string-key", "value") => empty collection
graph.getVertices("string-key", "value") => collection containing v1
graph.getVertices("string-key", null) => collection containing v1

I would expect the create and query interfaces to behave the same. Either throwing an error when you try to create a property key that needs to be escaped, or handling the escaping on query.

Steps to reproduce the problem

See above.

@tglman tglman added the bug label Jan 30, 2017

@tglman tglman self-assigned this Jan 30, 2017

@tglman

This comment has been minimized.

Show comment
Hide comment
@tglman

tglman Jan 30, 2017

Member

hi @shooit,

Thank you for reporting this, anyway the 2.1.x is out of support, so i would suggest you to plan a migration to 2.2.x, we will get this fixed in 2.2.x.

Regards

Member

tglman commented Jan 30, 2017

hi @shooit,

Thank you for reporting this, anyway the 2.1.x is out of support, so i would suggest you to plan a migration to 2.2.x, we will get this fixed in 2.2.x.

Regards

@tglman tglman added this to the 2.2.x (next hotfix) milestone Jan 30, 2017

@shooit

This comment has been minimized.

Show comment
Hide comment
@shooit

shooit Jan 30, 2017

Oops, I am actually on 2.2.14. The checkbox options confused me. Thanks!

shooit commented Jan 30, 2017

Oops, I am actually on 2.2.14. The checkbox options confused me. Thanks!

@tglman

This comment has been minimized.

Show comment
Hide comment
@tglman

tglman Jan 30, 2017

Member

hi @shooit,

Gotcha, just fixed and pushed.

here is the commit: 7b0e11d (just wrong issue id, but i cannot change it anymore ;( )

Member

tglman commented Jan 30, 2017

hi @shooit,

Gotcha, just fixed and pushed.

here is the commit: 7b0e11d (just wrong issue id, but i cannot change it anymore ;( )

@tglman tglman added the resolved label Jan 30, 2017

@shooit

This comment has been minimized.

Show comment
Hide comment
@shooit

shooit Jan 30, 2017

Thank you!

shooit commented Jan 30, 2017

Thank you!

@santo-it santo-it modified the milestones: 2.2.16, 2.2.x (next hotfix) Jan 30, 2017

@santo-it

This comment has been minimized.

Show comment
Hide comment
@santo-it

santo-it Jan 30, 2017

Contributor

Hi @shooit , thanks again for opening this issue

The fix has been noted in the Release Notes page. You may want to test a 2.2.16-SNAPSHOT or wait for the official 2.2.16 release

I'm closing this now. In case you still experience problems, please let us know

Thanks,

Contributor

santo-it commented Jan 30, 2017

Hi @shooit , thanks again for opening this issue

The fix has been noted in the Release Notes page. You may want to test a 2.2.16-SNAPSHOT or wait for the official 2.2.16 release

I'm closing this now. In case you still experience problems, please let us know

Thanks,

@santo-it santo-it closed this Jan 30, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment