[
https://issues.apache.org/jira/browse/SOLR-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15117197#comment-15117197
]
Joel Bernstein edited comment on SOLR-8518 at 1/26/16 1:47 PM:
---------------------------------------------------------------
Before we commit to this approach I have a question.
How much of the Catalog (DatabaseMetaData) information are we going to need to
get DBVisualizer working?
If we're going to need to get the DatabaseMetaData working for SOLR-8502 then
it makes sense to populate the column types directly from the Catalog. But if
we can close out SOLR-8502 without digging into the DatabaseMetaData then let's
take that the first Tuple approach in the latest patch.
was (Author: joel.bernstein):
Before we commit to this approach I have a question.
How much of the Catalog (DatabaseMetaData) information are we going to need to
get DBVisualizer working?
If we're going to need to get this working for SOLR-8502 then it makes sense to
populate the column types directly from the Catalog. But if we can close out
SOLR-8502 without digging into the DatabaseMetaData then let's take that the
first Tuple approach in the latest patch.
> Implement ResultSetMetaDataImpl getColumnType and getColumnTypeName
> -------------------------------------------------------------------
>
> Key: SOLR-8518
> URL: https://issues.apache.org/jira/browse/SOLR-8518
> Project: Solr
> Issue Type: Sub-task
> Components: SolrJ
> Affects Versions: Trunk
> Reporter: Kevin Risden
> Attachments: SOLR-8518.patch
>
>
> DBVisualizer uses getColumnType and getColumnTypeName to determine which
> ResultSetImpl.get* method to use when displaying the data otherwise it falls
> back to ResultSetImpl.getObject.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
