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
This due to the mess with LiteralInCollectionUpdaterProperty where I put one property going from index to value, and another going from value to true. Ah, come on, let me exemplify it.
Suppose you have a collection desrcibed as this Groovy array
[2, 5]
That's to say where value at index 0 is 2 and value at index 1 is 5. In such a case, gaedo will write the following properties
Notice that, due to company bandwidth limitation, #83 will not yet be fixed (as it would require migrating all of our graphs, which our QA not yet tolerates). Fix is however expected to happen soon ...
This due to the mess with
LiteralInCollectionUpdaterProperty
where I put one property going fromindex
to value, and another going from value totrue
. Ah, come on, let me exemplify it.Suppose you have a collection desrcibed as this Groovy array
That's to say where value at index
0
is2
and value at index1
is5
. In such a case, gaedo will write the following propertiesNow suppose collection is
It will translate as
You see the mess ? property names are identical, which result into neo4j rewriting properties as
Which in turn makes loading this collection having as values
Which do not translate to integer. Too bad. Solution ? Writing indexing properties ONLY in indices. Implementation ? Fucking hard.
The text was updated successfully, but these errors were encountered: