[
https://issues.apache.org/jira/browse/DERBY-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171603#comment-14171603
]
Rick Hillegas commented on DERBY-6763:
--------------------------------------
Hi Mark,
There is a TRANSLATE operator defined by the 2011 SQL Standard 6.30 (string
value function). It has the form
{noformat}
TRANSLATE( characterStringExpression USING transliterationName )
{noformat}
Is that the operator you had in mind? That would be well within Derby's
charter. Or were you thinking of implementing DB2's SYSIBM.TRANSLATE function?
I would not object to the latter provided that it lived in the SYSIBM schema.
Thanks,
-Rick
> Allow users to specify TRANSLATE function
> -----------------------------------------
>
> Key: DERBY-6763
> URL: https://issues.apache.org/jira/browse/DERBY-6763
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.11.1.1
> Reporter: Mark Buyukisik
> Priority: Minor
>
> I was wondering if Derby could please allow users to specify a TRANSLATE
> function. It does not look like one exists but when I try to create one I am
> denied because TRANSLATE is a reserved word. Right now we are using Derby as
> an embedded database used for local development and DAO impl testing (DB2 is
> used for official testing and production) and would like to be able to
> specify this function so our SQL statements work against both Derby and DB2.
> Thanks,
> Mark
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
