| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Florian Pflug <fgp(at)phlo(dot)org> |
| Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, cbbrowne(at)gmail(dot)com, alex-goncharov(at)comcast(dot)net, mmoncure(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable |
| Date: | 2011-10-09 15:56:56 |
| Message-ID: | 3936.1318175816@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Florian Pflug <fgp(at)phlo(dot)org> writes:
> On Oct9, 2011, at 14:20 , Kevin Grittner wrote:
>> Yeah. It would be nice to see at least one use case. The only
>> comment I recall is a vague suggestion that that people might want to
>> select data from a table and infer table attributes from the result
>> set metadata. That seems marginal.
> Well, there is one other, namely SQL standards compliance. It does
> mandate that "CREATE TABLE ... AS SELECT" creates NOT NULL constraints
> on non-nullable columns I think (I didn't re-check, though). I'm not sure
> I see the value in that either, but, hey, standards compliance ought
> to be a value it in itself, right?
Um ... but that case has nothing to do with protocol changes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-10-09 15:58:59 | Re: Schema grants for creating and dropping objects |
| Previous Message | Tom Lane | 2011-10-09 15:51:47 | Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable |