From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Deepak Beehyv <deepakram(dot)beehyv(at)alationdata(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org, venky(dot)ganti(at)alation(dot)com, nishanth beehyv <nishanth(dot)beehyv(at)alationdata(dot)com>, Dheeraj Beehyv <dheerajgoud(dot)beehyv(at)alationdata(dot)com> |
Subject: | Re: Regarding inclusion of indexes as tables |
Date: | 2015-05-08 16:46:11 |
Message-ID: | CAKFQuwYfej7bZY2+fcQ6X7zQj=pbNBrS3dq+zM7JDK49LaB4tg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Fri, May 8, 2015 at 4:40 AM, Deepak Beehyv <
deepakram(dot)beehyv(at)alationdata(dot)com> wrote:
> Hi all,
> We are trying to use the getColumns() and getTables() functions from
> DatabaseMetaData, but we are getting indexes as well in getTables() and
> indexColumns from getColumns() call. We are able to filter out indexes from
> getTables using tableType column available but were unable to do that for
> columns as tableType is not captured.
> I would like to know if getting indexes in getTables() and indexColumns in
> getColumns is warranted or a bug. If such a behaviour is warranted, is
> there any alternate solution.
>
>
Just thinking here...
Identify the table types you care about and create an array of them to
pass to "getTables()". For each of the tables returned pass the name of
the table to "getColumns()".
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Rotteveel | 2015-05-09 08:00:15 | Re: Regarding inclusion of indexes as tables |
Previous Message | dmp | 2015-05-08 16:45:45 | Re: Regarding inclusion of indexes as tables |