db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4230) DatabaseMetaData.getColumns() returns extra column from view with group by and expression in SELECT list
Date Tue, 19 May 2009 20:17:45 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kathey Marsden updated DERBY-4230:

    Attachment: DERBY-4230_preview_diff.txt

Here is my initial attempt at a fix for this issue. DERBY-4230_preview_diff.txt.  This is
*not* for commit as I still need to add a regression test and run tests.  I just thought I
would put it out there to make sure I am on the right track.

The code that defines the columns for insert in to SYS.SYSCOLUMNS was including the generated
columns. I changed it so that it no longer includes the generated columns and the test case
passes.  Are the SYS.SYSCOLUMN entries for views only used for DatabaseMetaData.getColumns()
 or is there some other use that might need the generated columns to be there?



> 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:
>            Reporter: Kathey Marsden
>            Assignee: Kathey Marsden
>         Attachments: create.sql, 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.

View raw message