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
@conker84 something interesting about the "intersection" in general is that there might be lists of mixed numbers. like doubles and longs and then folks might expect cypher semantics of 1.0 == 1.
But we should cover that in a separate issue I think.
Where we could have an separate method or means, e.g. by converting a list of numbers into a list of doubles or longs and then doing the intersection.
There is also the option of having a more lenient comparator which uses the default comparator as long as both values are the same type and the double comparator when it's mixed types.
The text was updated successfully, but these errors were encountered:
With the new versions of Cypher is no longer needed.
For example, executing the following 2 queries, the result is [2,3] for both of them
RETURN apoc.coll.intersection([1,2,3],[3,2]) AS value; // with 2 and 2 values
RETURN apoc.coll.intersection([1,2,3],[3,2.0]) AS value; // with 2 and 2.0 values
@conker84 something interesting about the "intersection" in general is that there might be lists of mixed numbers. like doubles and longs and then folks might expect cypher semantics of
1.0 == 1
.But we should cover that in a separate issue I think.
Where we could have an separate method or means, e.g. by converting a list of numbers into a list of doubles or longs and then doing the intersection.
There is also the option of having a more lenient comparator which uses the default comparator as long as both values are the same type and the double comparator when it's mixed types.
The text was updated successfully, but these errors were encountered: