[
https://issues.apache.org/jira/browse/DERBY-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-2526:
----------------------------------
Attachment: TestDerby.java
A user hit this bug in 10.1 but the symptom was different. Instead of wrong
results, they got a message: The repro is attached as TestDerby.java
Exception in thread "main" ERROR 42818: Comparisons between
'CHAR () FOR BIT DATA' and 'CHAR' are not supported.
at
org.apache.derby.iapi.error.StandardException.newException(Unkno
wn Source)
at
org.apache.derby.impl.sql.compile.BinaryComparisonOperatorNode.b
indComparisonOperator
(Unknown Source)
at
org.apache.derby.impl.sql.compile.PredicateList.searchClauseTran
sitiveClosure(Unknown
Source)
at
org.apache.derby.impl.sql.compile.SelectNode.performTransitiveCl
osure(Unknown Source)
at
org.apache.derby.impl.sql.compile.SelectNode.preprocess(Unknown
Source)
at
org.apache.derby.impl.sql.compile.DMLStatementNode.optimize(Unkn
own Source)
at
org.apache.derby.impl.sql.compile.CursorNode.optimize(Unknown
Source)
at
org.apache.derby.impl.sql.GenericStatement.prepMinion(Unknown
Source)
at
org.apache.derby.impl.sql.GenericStatement.prepare(Unknown
Source)
at
org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.
prepareInternalStatem
ent(Unknown Source)
at
org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown
Source)
at
org.apache.derby.impl.jdbc.EmbedStatement.executeQuery(Unknown
Source)
I'll look into backporting this fix to 10.2 and 10.1
> Wrong results with queries that use the JOIN ... ON syntax to join with views
> or other non-base table expressions.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2526
> URL: https://issues.apache.org/jira/browse/DERBY-2526
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.0.2.1, 10.1.3.1, 10.2.2.0, 10.3.1.4
> Reporter: Bryan Pendleton
> Assignee: A B
> Fix For: 10.3.1.4
>
> Attachments: badQuery.log, d2526_v1.html, d2526_v1.patch,
> d2526_v2.patch, d2526_v2.stat, derby-2526.sql, DistinctTestNotes.txt,
> firstTryPatch.diff, goodQuery.log, releaseNote.html, releaseNote.html,
> TestDerby.java
>
>
> I think both select statements in the attached repro script should return 1
> row, but in fact the first statement returns 1 row and the second returns
> zero rows.
> The only difference between the two statements is that the columns in the
> UNION view are listed in a different order (bvw vs. bvw2).
> This seems like a bug to me; the order of the columns in the view definition
> shouldn't matter, should it?
> As Army noted on the derby-dev list, the fact that this reproduces with 10.0
> means that it is not caused by some of the 10.2 optimizer changes. Something
> else is going wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
