| From: | Deepak Beehyv <deepakram(dot)beehyv(at)alationdata(dot)com> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Cc: | 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: | Regarding inclusion of indexes as tables |
| Date: | 2015-05-08 11:40:06 |
| Message-ID: | CAAuCDTi5_KRTUZabmdUVO9GESoPqkAc7atvCGNddExnzEcOwEQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
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.
--
regards
N.Deepak Ram
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dmp | 2015-05-08 16:45:45 | Re: Regarding inclusion of indexes as tables |
| Previous Message | Jeremy Whiting | 2015-05-05 20:49:49 | Re: Resource lookup timeout causes Travis IC to fail test. |