loxai
commented
11 years ago as discussed in https://groups.google.com/forum/?fromgroups=#!topic/neo4j/9O-L0ZGE93g the issue might be due to changes in neo4j 1.9 and neoclipse using 1.8
Open loxai opened 11 years ago
loxai
commented
11 years ago as discussed in https://groups.google.com/forum/?fromgroups=#!topic/neo4j/9O-L0ZGE93g the issue might be due to changes in neo4j 1.9 and neoclipse using 1.8
Using the neo4j java api (1.9) I set a node property to a certain string which results in an unreadable graph: node.setProperty("badProperty", "d64704f2bfb95a50f083f4091b490d47688a998c");
adding or removing a few chars, or setting a char to a hypen (like node.setProperty("okProperty", "-64704f2bfb95a50f083f4091b490d47688a998c");) works fine, which makes me think problem relates to inline string compression. Setting the mischievous string directly from Neoclipse works fine (no error thrown and the whole graph is visible afterwards).