[
https://issues.apache.org/jira/browse/DERBY-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712038#action_12712038
]
Knut Anders Hatlen commented on DERBY-4230:
-------------------------------------------
Sounds fine. The problem with ORDER BY columns can be addressed when/if we
allow ORDER BY in CREATE VIEW.
> DatabaseMetaData.getColumns() returns extra column from view with group by
> and expression in SELECT list
> ---------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4230
> URL: https://issues.apache.org/jira/browse/DERBY-4230
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.2.1
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Attachments: create.sql, DERBY-4230_diff.txt,
> DERBY-4230_preview_diff.txt, ViewTest.java
>
>
> DatabaseMetaData.getColumns() returns an extra column for a view with a group
> by and an expression in the select list. I will attach the reproduction. Run
> the script create.sql and then the program ViewTest.
> This is a regression in version 10.3, It ran ok on latest on the 10.1 and
> 10.2 branches.
> The ResultSetMetaData appears to return the correct number of columns when
> you select from the view, but it would be nice to add a regression test for
> that too.
> See discussion on derby-dev.
> http://www.nabble.com/extra-column-in-DatabaseMetaData.getColumns()-with-group-by-in-view-td23545576.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
