Closed mattfiocca closed 8 years ago
Thanks for the report, I'll investigate.
@mattfiocca What version of the client/driver are you using ? It reminds me a same bug reported a while back
@mattfiocca Yeah actually I think it is fixed already :
https://github.com/graphaware/neo4j-bolt-php/commit/0a941a82f5fc0a6ddaf0f7a90ae0335063b0e933
I suggest you update your dependencies :
rm -rf composer.lock
composer update graphaware/neo4j-php-client
I'm running 4.4 of the client. Looking at composer.json
of the client that i've got though, its listing version ^1.0
of bolt, and not ^1.5
.... After clearing my lock file and re-updating, nothing seems to happen with composer though. I'm not a huge composer expert, do you know of any other way to force update the graphaware packages? I appreciate the help
I was able to get composer to download the correct versions by rm -rf ~/.composer
entirely first. I had read to try rm -rf ~/.composer/cache
, but I had to remove the entire thing in order to get the packages to download again. thanks for helping me,
I'm having a really hard time narrowing down why I am getting serialization errors when running cypher queries on specific node labels through a neo4j-php-client stack over bolt.
When I run:
I get this exception:
But when i run this on a different node label:
The query works as expected.
Does this mean something is up with the data in one of my LOCATION nodes somehow? If so, what would cause serialization errors within my nodes? Everything works fine when i connect using the default http protocol, this only applies to bolt connections.
Here are the properties of the LOCATION node that the query chokes on:
And here are the properties of the REPORT node that works just fine:
Any and all advice is welcome.