[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-184) Add boolean anddatetime literals to query grammar
[ http://tools.oasis-open.org/issues/browse/CMIS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11603#action_11603 ] Florent Guillaume commented on CMIS-184: ---------------------------------------- Ok then I propose that we follow the JCR and use its format (subset of ISO 8601), with a TIMESTAMP prefix: <datetime literal> ::= TIMESTAMP <quote> <datetime string> <quote> <datetime string> ::= !! As defined by JCR, YYYY-MM-DDThh:mm:ss.sssTZD with TZD = Z or +hh:mm or -hh:mm Note that in this JCR format the .sss is not optional, there's always 3 decimal places. > Add boolean and datetime literals to query grammar > -------------------------------------------------- > > Key: CMIS-184 > URL: http://tools.oasis-open.org/issues/browse/CMIS-184 > Project: OASIS Content Management Interoperability Services (CMIS) TC > Issue Type: Bug > Reporter: Florian Mueller > > The current query grammar just allows numeric literals and string literals to be used in comparisons: > <comparison predicate> ::= <value expression> <comp op> <literal> > <literal> ::= <signed numeric literal> | <character string literal> > <signed numeric literal> ::= !! As defined by SQL-92 grammar. > <character string literal> ::= !! As defined by SQL-92 grammar. > We should add support for boolean and datetime literals. That implies that we have to define a one or more valid formats for datetime literals. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]