Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collection of Integers (like a List<Integer> are not supported as of now #83

Open
Riduidel opened this issue Mar 28, 2014 · 0 comments
Open
Labels

Comments

@Riduidel
Copy link
Owner

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

 myCollection.size=2
 myCollection:0=2
 myCollection:1=5
 myCollection:2=true
 myCollection:5=true

Now suppose collection is

 [1,0]

It will translate as

myCollection.size=2
myCollection:0=1
myCollection:1=0
myCollection:1=true
myCollection:0=true

You see the mess ? property names are identical, which result into neo4j rewriting properties as

myCollection:1=true
myCollection:0=true

Which in turn makes loading this collection having as values

[true, true]

Which do not translate to integer. Too bad. Solution ? Writing indexing properties ONLY in indices. Implementation ? Fucking hard.

@Riduidel Riduidel added the bug label Mar 28, 2014
Riduidel pushed a commit that referenced this issue Mar 28, 2014
…ctly loaded.

This fix also introduces elements of correction for #83 (by distinguishing property valyes and property indexing values.
Riduidel pushed a commit that referenced this issue Apr 2, 2014
…sue to take this form ...

But well, I'm not totally surprised.
Riduidel pushed a commit that referenced this issue Apr 2, 2014
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 ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant