[
https://issues.apache.org/jira/browse/DERBY-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485406
]
Daniel John Debrunner commented on DERBY-1949:
----------------------------------------------
Why is this bug marked "Existing application impact"? There's no code changes
right?
Also I'm not sure marking this fixed is correct, because the issue as described
in the summary was not fixed.
I agree it was good to make documentation changes, but this will now appear of
the list of fixed bugs for 10.3
as the current summary. Maybe invalid is a better status even if changes were
made?
> locate function returns invalid value when first parameter is empty string
> --------------------------------------------------------------------------
>
> Key: DERBY-1949
> URL: https://issues.apache.org/jira/browse/DERBY-1949
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.1.3.1, 10.2.1.6
> Environment: N/A
> Reporter: Oleksandr Alesinskyy
> Assigned To: Bryan Pendleton
> Fix For: 10.3.0.0
>
> Attachments: docs.diff, docs_v2.diff, rrefsqlj61998.html,
> rrefsqlj61998.html
>
>
> locate function returns false invalid when first parameter is empty string,
> e.g.
> values(locate('','A')
> results in 1, which is obviously wrong
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
