| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Dann Corbit" <DCorbit(at)connx(dot)com> |
| Cc: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Gregory Stark" <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org, "Larry McGhaw" <lmcghaw(at)connx(dot)com> |
| Subject: | Re: Selecting a constant question |
| Date: | 2007-06-11 22:49:52 |
| Message-ID: | 26927.1181602192@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Dann Corbit" <DCorbit(at)connx(dot)com> writes:
>> To be honest, the concept that a widget requires a constant that can't
>> be changed later is also a bit odd.
> Not when the data itself is a constant that cannot be changed.
Surely this case is not sufficiently important to justify designing
your entire application (not to mention the client/server protocol)
around it. You're always going to have variable-width columns in there
somewhere.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dann Corbit | 2007-06-11 22:53:13 | Re: Got no response last time on setsockopt post, so I thought I would reiterate. |
| Previous Message | Alvaro Herrera | 2007-06-11 22:43:37 | Re: Selecting a constant question |