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 ` { code}{ 0} ` , ` {1} ` {code} 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 |
|
