| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org, Alex Goncharov <alex-goncharov(at)comcast(dot)net> |
| Cc: | Florian Pflug <fgp(at)phlo(dot)org> |
| Subject: | Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable |
| Date: | 2011-10-07 00:28:30 |
| Message-ID: | 201110070228.31832.andres@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Goncharov | 2011-10-07 00:34:41 | Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable |
| Previous Message | Alex Goncharov | 2011-10-07 00:20:31 | Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable |