[
https://issues.apache.org/jira/browse/PHOENIX-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932985#comment-13932985
]
Gabriel Reid commented on PHOENIX-843:
--------------------------------------
{quote}Are we doing the right thing for the type name? Is should come out as
INTEGER ARRAY or INTEGER[] ?{quote}
I don't think there's really a "correct" type name, as it's supposedly a
database-specific name, but from what I've seen the most standard naming
strategy used by other DBs is "INTEGER ARRAY".
{quote}I suspect DatabaseMetaData#getColumns is returning our special type ID
too.{quote}
I'll double check that, and post an updated patch if it's returning the
internal id.
{quote}I'm curious - what tools are you finding have support for ARRAY?{quote}
Currently accessing Phoenix via Optiq. Optiq has some support for arrays (I'm
working on improving that), but the biggest issue is that Optiq (and possibly
other tooling) has no idea what to do if it gets a type id that isn't in
java.sql.Types.
> Incorrect java.sql.Types value returned for array types in result set
> ---------------------------------------------------------------------
>
> Key: PHOENIX-843
> URL: https://issues.apache.org/jira/browse/PHOENIX-843
> Project: Phoenix
> Issue Type: Bug
> Reporter: Gabriel Reid
> Attachments: PHOENIX-843.patch
>
>
> All array PDataTypes currently return their Phoenix-specific type constant in
> PDataType#getResultSetSqlType. This causes issues with external tools which
> aren't familiar with the Phoenix array types, so java.sql.Types.ARRAY should
> be returned for array types instead.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
