[
https://issues.apache.org/jira/browse/DERBY-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-5837:
-----------------------------------
Labels: derby_triage10_10 feature (was: )
> Add support for SQL standard DATE, TIME, TIMESTAMP literals
> -----------------------------------------------------------
>
> Key: DERBY-5837
> URL: https://issues.apache.org/jira/browse/DERBY-5837
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.8.2.2
> Reporter: Lukas Eder
> Priority: Minor
> Labels: derby_triage10_10, feature
>
> The SQL standard 1992 specifies <datetime literals> as such:
> <datetime literal> ::=
> <date literal>
> | <time literal>
> | <timestamp literal>
> <date literal> ::=
> DATE <date string>
> <time literal> ::=
> TIME <time string>
> <timestamp literal> ::=
> TIMESTAMP <timestamp string>
> <date string> ::=
> <quote> <date value> <quote>
> <time string> ::=
> <quote> <time value> [ <time zone interval> ] <quote>
> <timestamp string> ::=
> <quote> <date value> <space> <time value> [ <time zone
> interval> ] <quote>
> Taken from:
> http://www.contrib.andrew.cmu.edu/~shadow/sql/sql1992.txt
> This seems not to be supported directly by Derby. Instead, Derby supports
> functions for constructing DATE, TIME, TIMESTAMP values. For example:
> http://db.apache.org/derby/docs/dev/ref/rreftimestampfunc.html
> For increased compatibility, it would be nice if literals were implemented
> according to the standard. In essence, the function's parentheses could be
> made optional
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
