Add boolean and datetime literals to query grammar

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Hide

      <comparison predicate> ::= <value expression> <comp op> <literal>
      <literal> ::= <signed numeric literal> | <character string literal> | <boolean literal> | <datetime literal>
      <signed numeric literal> ::= !! As defined by SQL-92 grammar.
      <character string literal> ::= !! As defined by SQL-92 grammar.
      <boolean literal> ::= TRUE | FALSE
      <datetime literal> ::= !! Format: YYYY-MM-DDThh:mm:ssTZD

      Show
      <comparison predicate> ::= <value expression> <comp op> <literal> <literal> ::= <signed numeric literal> | <character string literal> | <boolean literal> | <datetime literal> <signed numeric literal> ::= !! As defined by SQL-92 grammar. <character string literal> ::= !! As defined by SQL-92 grammar. <boolean literal> ::= TRUE | FALSE <datetime literal> ::= !! Format: YYYY-MM-DDThh:mm:ssTZD

      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.

            Assignee:
            Unassigned
            Reporter:
            Florian Müller (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: