Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: SQL
    • Labels:
      None

      Description

      It would be good to have a built-in HEX function, or another method to create character values with arbitrary ASCII values (e.g. TAB, CR/LF, etc.).

      If "CHAR FOR BIT DATA" values could be converted to CHAR or VARCHAR, the x'...' syntax could be used to create binary character constants. But I found no way to convert "CHAR FOR BIT DATA" to CHAR.

      I didn't find an explicit description of the X'...' syntax in the reference manual. The only 2 occurences are in the SQL examples of the LENGTH function ("VALUES LENGTH(X'FF')") and of the "CHAR FOR BIT DATA" data type ("INSERT INTO t VALUES (X'DE');"). Is the x'...' syntax an unwanted remains from an old Cloudscape version, or will it still be supported (and properly documeted) in future Derby versions?

        Issue Links

          Activity

          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open Closed Closed
          3037d 12h 46m 1 Knut Anders Hatlen 12/Mar/13 11:44
          Gavin made changes -
          Workflow jira [ 38424 ] Default workflow, editable Closed status [ 12802421 ]
          Knut Anders Hatlen made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Resolution Duplicate [ 3 ]
          Knut Anders Hatlen made changes -
          Link This issue duplicates DERBY-1360 [ DERBY-1360 ]
          Hide
          Knut Anders Hatlen added a comment -

          DERBY-1360 tracks the request for Unicode character literals. As Dag points out, that would be the preferred way to implement the functionality requested here, so I'm closing this issue for now. Further discussion could continue over at DERBY-1360.

          Show
          Knut Anders Hatlen added a comment - DERBY-1360 tracks the request for Unicode character literals. As Dag points out, that would be the preferred way to implement the functionality requested here, so I'm closing this issue for now. Further discussion could continue over at DERBY-1360 .
          Hide
          Dag H. Wanvik added a comment -

          I think we would rather want to support the standard <Unicode character string literal>, which would allow hex escapes, e.g.

          U&"b\00E5t" giving "båt"

          or

          U&"b|00E5t" UESCAPE '|' where we choose a non-default quote character.

          Show
          Dag H. Wanvik added a comment - I think we would rather want to support the standard <Unicode character string literal>, which would allow hex escapes, e.g. U&"b\00E5t" giving "båt" or U&"b|00E5t" UESCAPE '|' where we choose a non-default quote character.
          Dag H. Wanvik made changes -
          Field Original Value New Value
          Issue Type New Feature [ 2 ] Improvement [ 4 ]
          Christian d'Heureuse created issue -

            People

            • Assignee:
              Unassigned
              Reporter:
              Christian d'Heureuse
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development