phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergio Lob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1420) DatabaseMetaData.getschemas returns incorrect column order
Date Fri, 07 Nov 2014 18:58:35 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14202452#comment-14202452
] 

Sergio Lob commented on PHOENIX-1420:
-------------------------------------

getSchema() answer set description in java doc does seem inconsistent with getTables , getColumns,
I grant you that. I would also have thought that catalog should go before schema.  The description
for getSchema seems to contradict this, however. As the java api doc is the 'standard', though,
it should not be left to the reader to reinterpret the documentation. Are you aware of any
other JDBC driver that sets the column-ordering this way?  

> DatabaseMetaData.getschemas returns incorrect column order
> ----------------------------------------------------------
>
>                 Key: PHOENIX-1420
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1420
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.1
>         Environment: all OS
>            Reporter: Sergio Lob
>
> DatabaseMetaData.getSchemas returns incorrect column order. According to java 6 api doc,
getSchemas should return answer set columns in the following order: 
>  
> 1.TABLE_SCHEM String => schema name 
> 2.TABLE_CATALOG String => catalog name
> The Phoenix JDBC driver returns these in reverse column order, i.e.
> 1. TABLE_CATALOG
> 2. TABLE_SCHEM
> Our experience with other JDBC drivers is that they return the data w/ TABLE_SCHEM being
the first column.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message