Re: Why are clobs always "0"

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Arnie Morein <arnie(dot)morein(at)mac(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Why are clobs always "0"
Date: 2019-12-01 18:21:41
Message-ID: f9202ff9-cbb2-c2d4-76b3-e18af3935ee4@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 12/1/19 9:31 AM, Arnie Morein wrote:
> I have tested the most recent driver in three different SQL IDEs, and
> now with an application I'm writing that uses JDBC metadata, the comment
> on a field definition also isn't available as a string value.
>
> The only thing I ever see regarding data type "text" field values are
> either a 0 or a 1; neither of which applies.
>
> So why is this happening, even from the JDBC metadata results as well?

You are going to have to be more specific:

1) You refer to clob, but the clob datatype is not supported:
https://www.postgresql.org/docs/11/unsupported-features-sql-standard.html
So what are you referring to?

2) Comment on field definition is what exactly?

3) How are you fetching the metadata?

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Andreas Joseph Krogh 2019-12-01 20:37:38 Sv: Why are clobs always "0"
Previous Message Alex O'Ree 2019-12-01 17:59:08 slow insert speeds with bytea