[
https://issues.apache.org/jira/browse/PHOENIX-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385044#comment-14385044
]
Carter Shanklin commented on PHOENIX-1781:
------------------------------------------
[~jamestaylor] Our interest in now() was motivated by the JDBC 3.0 spec (see
Appendix C.3 of http://java.cnam.fr/iagl/biblio/spec/jdbc-3_0-fr-spec.pdf) and
some analysis of a corpus of ~1500 SQL samples downloaded from pastebin.
An except of that analysis over the Section C.3 functions is:
|Function|Area|ScriptHits|
|NOW|Date|71|
|YEAR|Date|69|
|MONTH|Date|53|
|SECOND|Date|25|
|CURDATE|Date|23|
|WEEK|Date|17|
|HOUR|Date|14|
I can elaborate more on the method if anyone cares. In any event many of these
functions have been flowing into Phoenix lately.
100% agree there is no value in an Oracle clone, the real motivation is that
now is very commonly used and it would make adopting Phoenix easier. FWIW
Postgres and MySQL both offer now() as well.
> Add Now()
> ---------
>
> Key: PHOENIX-1781
> URL: https://issues.apache.org/jira/browse/PHOENIX-1781
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Alicia Ying Shu
> Assignee: Alicia Ying Shu
>
> Phoenix currently supports current_date() that returns a timestamp.
> From Oracle doc:
> NOW() A timestamp value representing the current date and
> time
> Many customers use Now() for current timestamp and curDate() for current
> Date. Will implement Now() similar to Phoenix current_date() so that
> customers do not need to change their queries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
