Re: Release 1204 released

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Mark Rotteveel <mark(at)lawinegevaar(dot)nl>
Cc: List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Release 1204 released
Date: 2015-10-16 10:43:54
Message-ID: CADK3HHJkf=o+FJbdg3YoRhmvy3dE+URTTkw0DGjQyH07ok0uhQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Here is the proposed PR https://github.com/pgjdbc/pgjdbc/pull/403

Please comment

Dave Cramer

davec(at)postgresintl(dot)com
www.postgresintl.com

On 16 October 2015 at 03:01, Mark Rotteveel <mark(at)lawinegevaar(dot)nl> wrote:

> 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
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Michał Niklas 2015-10-16 11:12:10 Re: Change of format of returned flat value after prepareThreshold
Previous Message Vladimir Sitnikov 2015-10-16 10:15:23 Re: Change of format of returned flat value after prepareThreshold