[
http://issues.apache.org/jira/browse/DERBY-402?page=comments#action_12422663 ]
Kathey Marsden commented on DERBY-402:
--
This patch posted in February, looks like it is ready for review but is
currently unassigned. Jeff submitted a patch b
[
http://issues.apache.org/jira/browse/DERBY-402?page=comments#action_12366854 ]
Satheesh Bandaram commented on DERBY-402:
-
Yes... I think so. I have not looked at what else need to be changed, but those
two paragraphs should go.
> INTERSECT/EXCEPT
[
http://issues.apache.org/jira/browse/DERBY-402?page=comments#action_12366845 ]
Jeff Levitt commented on DERBY-402:
---
So I'm trying to understand the doc impact of this bug. Should the offending
sentences just be removed?
Thanks!
> INTERSECT/EXCEPT/UNI
[
http://issues.apache.org/jira/browse/DERBY-402?page=comments#action_12366520 ]
Satheesh Bandaram commented on DERBY-402:
-
You probably know this already, Derby does return the first expression column
name if it matches all other expression column
[
http://issues.apache.org/jira/browse/DERBY-402?page=comments#action_12366494 ]
Alex Miller commented on DERBY-402:
---
The SQL spec basically says that if the column names at the ith position of the
different query expressions in the union don't match, it
[
http://issues.apache.org/jira/browse/DERBY-402?page=comments#action_12314658 ]
Satheesh Bandaram commented on DERBY-402:
-
I believe both these are documentation errors, not code issues. Derby tries to
generate a result name if both sides of UNION
