[
https://issues.apache.org/jira/browse/DERBY-4793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-4793:
---------------------------------
Urgency: Low
Bug behavior facts: [Deviation from standard]
Labels: derby_triage10_8 (was: )
Tentatively marking as "deviation from standard", I tend to agree with Knu't
conclusion that it should be disallowed if the concatenated string doesn't fit
in a legal SQL type (VARCHAR).
> Assert failure when concatenating strings with total size greater than 32K
> --------------------------------------------------------------------------
>
> Key: DERBY-4793
> URL: https://issues.apache.org/jira/browse/DERBY-4793
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.6.1.0
> Reporter: Knut Anders Hatlen
> Labels: derby_triage10_8
> Attachments: concat.sql
>
>
> When concatenating two strings whose total length exceeds the maximum length
> for a VARCHAR, an assert is triggered in the debug jars:
> ij> values length('0123456789.....' || '0123456789.....');
> ERROR XJ001: Java exception: 'ASSERT FAILED The maximum length 35000 for the
> result type VARCHAR can't be greater than it's maximum width of result's
> typeid32672: org.apache.derby.shared.common.sanity.AssertFailure'.
> With non-debug jars, the same query completes successfully:
> ij> values length('0123456789.....' || '0123456789.....');
> 1
> -----------
> 35000
> 1 row selected
> I think this query is supposed to fail, also with non-debug jars, but in any
> even it shouldn't be raising assert failures.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
