From: | Mark Rotteveel <mark(at)lawinegevaar(dot)nl> |
---|---|
To: | <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Release 1204 released |
Date: | 2015-10-16 07:01:26 |
Message-ID: | 51093c12dca2bcd9a042e2cb92b66551@imap.procolix.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Fri, 16 Oct 2015 08:50:47 +0200, Thomas Kellerer <spam_eater(at)gmx(dot)net>
wrote:
> Interesting issue - that is indeed a use-case I didn't think about.
>
> It's too bad that getColumns() doesn't return a "TABLE_TYPE" column that
> would match the types returned by getTableTypes()
>
> However, information_schema.columns does return columns from views, so
> those should at least be included
> (although not getting columns for materialized views or types would mean
I
> had to adjust my SQL Workbench for that)
As I understand it, materialized views are a type of table (or maybe a
special type of view), and therefor should be returned by getTables. A JDBC
driver is free to define additional table types, as long as those types
behave like tables (as in: can be selected). Not sure how that works for
types.
Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Vladimir Sitnikov | 2015-10-16 10:15:23 | Re: Change of format of returned flat value after prepareThreshold |
Previous Message | Mark Rotteveel | 2015-10-16 06:57:11 | Re: Release 1204 released |