[
https://issues.apache.org/jira/browse/PHOENIX-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyle Buzsaki updated PHOENIX-1002:
----------------------------------
Attachment: PHOENIX-1002_3.patch
Added type checking and order of operations tests for the modulus operator.
It's still built on the modulus function, but is it really worth removing the
modulus function compared to just having both?
The attached patch is compared against my patch fixing operator precedence at
PHOENIX-1075
> Add support for % operator
> --------------------------
>
> Key: PHOENIX-1002
> URL: https://issues.apache.org/jira/browse/PHOENIX-1002
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Thomas D'Silva
> Attachments: PHOENIX-1002.patch, PHOENIX-1002_2.patch,
> PHOENIX-1002_3.patch
>
>
> Supporting the % operator would allow using sequences to generate IDs that
> are less than a maximum number.
> CREATE SEQUENCE foo.bar
> SELECT ((NEXT VALUE FOR foo.bar)%1000)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
