phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <>
Subject [jira] [Updated] (PHOENIX-952) Support ANY and ALL built-ins for ARRAYs
Date Wed, 11 Jun 2014 12:43:02 GMT


ramkrishna.s.vasudevan updated PHOENIX-952:

    Attachment: Phoenix-952_5.patch

Updated patch.  Actually thought not to use ARRAY_ELM_REF in this but add a new node and a
new expression.  Then decided not to do that(as per your suggestion). If needed can even add
a new node and an expression for that and use instead of ARRAY_ELEM_REF.
The ArrayAny(All)Expression creates a loop and inside it forms a new ComparisonExpression
so that the evaluate() would be able to fetch every element in the Array and then do the comparison
on that. 
ArrayAllExpression is a subclass of ArrayAnyExpression and what to return as a result after
comparison (true or false) is actually overridden.

> Support ANY and ALL built-ins for ARRAYs
> ----------------------------------------
>                 Key: PHOENIX-952
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 3.0.0, 4.0.0
>            Reporter: James Taylor
>            Assignee: ramkrishna.s.vasudevan
>             Fix For: 3.1, 4.1
>         Attachments: Phoenix-932_1.patch, Phoenix-932_2.patch, Phoenix-952_4.patch, Phoenix-952_5.patch
> There's currently no good way to search array elements. We should support the ANY and
ALL built-ins for our ARRAY type like Postgres does:

This message was sent by Atlassian JIRA

View raw message