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

From: "anarazel(at)anarazel(dot)de" <andres(at)anarazel(dot)de>
To: Alex Goncharov <alex-goncharov(at)comcast(dot)net>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable
Date: 2011-10-07 00:54:39
Message-ID: 9e1e6439-f1b5-44c7-a530-32f43c819e39@email.android.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alex Goncharov <alex-goncharov(at)comcast(dot)net> schrieb:

>,--- You/Andres (Fri, 7 Oct 2011 02:28:30 +0200) ----*
>| > a lot of cases where the database could deduce (quite easily) that
>a
>| > result column cannot be null
>| Could you quickly explain what exactly you want that information for?
>Just
>| because it has been done before doesn't necessarily mean its a good
>idea...
>
>I am not writing a database application here (i.e. I am not storing
>the data). I am responding to a client requirement, basically:
>
> Given a SELECT (or possibly, simpler, a table name), tell me which
> columns are non-nullable?
That doesnt explain why it's needed. To get community buyin into a feature the community - or at least parts of it - need to understand why its needed.

Greetings, Andres

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alex Goncharov 2011-10-07 01:05:55 Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable
Previous Message Alex Goncharov 2011-10-07 00:46:47 Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable