We're updating the issue view to help you get more done. 

Support Cypher queries with positional parameters for Neo4j or throw a clear exception when the user tries to run it

Description

We should at least throw a clear exception with a message that explain that this is not working at the moment.
MongoDB already does that.

It should be possible to implement this for Cypher queries with Neo4j becaus ecypher queries accept parameters in the form of

1 {0}, {1}

and so on.

If the work on this issues is done after the update to Hibernate ORM 5.3 we also need to keep track of the property in sessionFactory.getSessionFactoryOptions().jdbcStyleParamsZeroBased() as in ParamLocationRecognizer.parseLocations

Environment

None

Status

Assignee

vk

Reporter

Davide D'Alto

Labels

None

Worked in

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Community Help Wanted

None

Suitable for new contributors

None

Requires Release Note

None

backportDecision

None

backportReEvaluate

None

Components

Fix versions

Priority

Major