Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Alex Goncharov <alex-goncharov(at)comcast(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable
Date: 2011-10-06 20:16:18
Message-ID: CAHyXU0yvk4vSL8rDRJvvY8rJQZMwxhkO5k3_QfnAzsuC4iARsg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 6, 2011 at 1:02 PM, Alex Goncharov
<alex-goncharov(at)comcast(dot)net> wrote:
> My understanding is that libpq does not allow one to find if a result
> set column is nullable.
>
> Is this right?
>
> (I know how to get a table column nullability information from
> pg_attribute.attnotnull, but when coding around the libpq API:
>
>  * Is, OMG, ugly.
>
>  * Doesn't cover the arbitrary SELECT statements.

why aren't you using PQgetisnull()?

merlin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2011-10-06 20:18:26 Re: index-only scans
Previous Message Pavel Stehule 2011-10-06 20:15:26 Re: [REVIEW] Patch for cursor calling with named parameters