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
I have noticed that executing queries from a NodeJS application, using neo4j-driver version 1.7.3, is not working against Neo4j database with version 3.5.2, for parameterized queries, like below:
`
// CASE 1 - promise based approach :
session.run( query, param ).then( ( result ) => {
console.log( result );
} )
.catch( err => console.log( err ) );
Both approaches log only query statistics, no results retrieved, although the same query executed on GrapheneDB client produces results.
Queries that do not have parameters execute as expected on Neo4j DB , version 3.5.2.
Both above approaches execute as expected against Neo4j database version 3.3.9, hosted on Graphene DB.
Is there any known compatibility issue between neo4j-driver, v1.73 and Neo4j Database, 3.5.2 ?
The text was updated successfully, but these errors were encountered:
Hi @cameliaben
In our tests, we have no problem to run parameterised queries against the database. 1.7 drivers are compatible with database 3.5 to 3.2 series.
For example the queries used in our examples are all verified.
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I have noticed that executing queries from a NodeJS application, using neo4j-driver version 1.7.3, is not working against Neo4j database with version 3.5.2, for parameterized queries, like below:
`
// CASE 1 - promise based approach :
session.run( query, param ).then( ( result ) => {
console.log( result );
} )
.catch( err => console.log( err ) );
//-----------------------------------------------------------------------
//CASE 2 - streaming-based approach:
session.run( query, param )
.subscribe ( {
onNext ( record ) {
console.log( record );
},
onCompleted ( result ) {
console.log( result );
session.close();
},
onError ( error ) {
console.log( error );
session.close();
},
} );`
Both approaches log only query statistics, no results retrieved, although the same query executed on GrapheneDB client produces results.
Queries that do not have parameters execute as expected on Neo4j DB , version 3.5.2.
Both above approaches execute as expected against Neo4j database version 3.3.9, hosted on Graphene DB.
Is there any known compatibility issue between neo4j-driver, v1.73 and Neo4j Database, 3.5.2 ?
The text was updated successfully, but these errors were encountered: