[
https://issues.apache.org/jira/browse/DERBY-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502467
]
A B commented on DERBY-1623:
----------------------------
> So is trim not a core function?
Sorry, I think I was confusing myself here. The issue I was trying to point
out is that the patch exposes the TRIM function through the JDBC escaped
function syntax, and I was wondering if that's correct--i.e. is TRIM actually a
JDBC escaped function, or is just an SQL function?
But it looks like this is an existing problem in the Derby handling of
functions, per DERBY-591. So technically that's a different issue. It'd be
nice if we could somehow avoid adding "TRIM" to the list of functions that are
already incorrectly exposed via JDBC escape syntax. If, however, you feel like
that's the out of the scope of this issue, then perhaps you could just add a
comment to DERBY-591 indicating that "TRIM" is now part of that list, as well?
> Add ANSI TRIM implementation
> ----------------------------
>
> Key: DERBY-1623
> URL: https://issues.apache.org/jira/browse/DERBY-1623
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Reporter: Emmanuel Bernard
> Assignee: Manish Khettry
> Attachments: 1623-parser-guess.diff, 1623.patch.txt,
> AnsiTrimTest.java, compile_error.jj, sqlgrammar.jj.diff
>
>
> JPA is requiring databases to support this ANSI feature esp the ability to
> chose the trimmed character
> TRIM([ [ LEADING | TRAILING | BOTH ] [ chars ] FROM ] str)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
