Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1CED4D829 for ; Tue, 12 Mar 2013 11:45:18 +0000 (UTC) Received: (qmail 1907 invoked by uid 500); 12 Mar 2013 11:45:17 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 469 invoked by uid 500); 12 Mar 2013 11:45:15 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 98997 invoked by uid 99); 12 Mar 2013 11:45:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Mar 2013 11:45:13 +0000 Date: Tue, 12 Mar 2013 11:45:13 +0000 (UTC) From: "Knut Anders Hatlen (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (DERBY-69) RFE: HEX function MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen closed DERBY-69. ----------------------------------- Resolution: Duplicate 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. > RFE: HEX function > ----------------- > > Key: DERBY-69 > URL: https://issues.apache.org/jira/browse/DERBY-69 > Project: Derby > Issue Type: Improvement > Components: SQL > Reporter: Christian d'Heureuse > > 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? -- 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