Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable - Mailing list pgsql-hackers

From Andres Freund
Subject Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable
Date
Msg-id 201110070228.31832.andres@anarazel.de
Whole thread Raw
In response to Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable  (Alex Goncharov <alex-goncharov@comcast.net>)
Responses Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable
List pgsql-hackers
On Friday, October 07, 2011 01:42:13 AM Alex Goncharov wrote:
> ,--- You/Florian (Fri, 7 Oct 2011 01:00:40 +0200) ----*
> 
> | On Oct7, 2011, at 00:02 , Alex Goncharov wrote:
> | > ,--- Florian Pflug (Thu, 6 Oct 2011 23:16:53 +0200) ----*
> | > 
> | > | Sure, but there are still a lot of cases where the database could
> | > | deduce (quite easily) that a result column cannot be null.
> | >
> | > 
> | >
> | > Right. Of course.  I can do it in 'psql'.
> |
> | 
> |
> | For the result of an arbitrary query?
> 
> In 'psql', no: I was commenting specifically, and confirming what you
> said, on your
> 
>  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...


Thanks,

Andres


pgsql-hackers by date:

Previous
From: Alex Goncharov
Date:
Subject: Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable
Next
From: Alex Goncharov
Date:
Subject: Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable