[
https://issues.apache.org/jira/browse/DERBY-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764923#action_12764923
]
Dag H. Wanvik commented on DERBY-4391:
--------------------------------------
> perhaps bulk-fetching is disabled when we have a correlated sub-query in the
> predicate list?
I don't know, but even if it is, I think it is more convoluted to rely on that
when pruning subquery visits.
So, your present patch in view of this is fine.
+1
Btw, I saw this inside setUnionResultExpression
/* DB2 requires both sides of union to have same name for the result to
* have that name. Otherwise, leave it or set it to a generated name */
Wonder what the standard says about this? (I came across it when playing with
Bryan's patch for DERBY-4).
> NullPointerException when comparing indexed column with result from a set
> operation
> -----------------------------------------------------------------------------------
>
> Key: DERBY-4391
> URL: https://issues.apache.org/jira/browse/DERBY-4391
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.2.2.0, 10.3.3.0, 10.4.2.0, 10.5.3.0, 10.6.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Attachments: d4391-1a.diff, d4391-1a.stat
>
>
> I'm reporting this issue on behalf of Bernt M. Johnsen.
> If an indexed column is compared with a UNION query (or some other set
> operation), a NullPointerException is raised, as can be seen by this sequence
> of statements in ij:
> ij> create table t(a int not null primary key, b int);
> 0 rows inserted/updated/deleted
> ij> select * from t where a < (values 4 union values 4);
> ERROR XJ001: Java exception: ': java.lang.NullPointerException'.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
