From: | "Dann Corbit" <DCorbit(at)connx(dot)com> |
---|---|
To: | "Kris Jurka" <books(at)ejurka(dot)com>, "Larry McGhaw" <lmcghaw(at)connx(dot)com> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Selecting a constant question |
Date: | 2007-06-12 00:11:04 |
Message-ID: | D425483C2C5C9F49B5B7A41F894415470100071E@postal.corporate.connx.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org [mailto:pgsql-hackers-
> owner(at)postgresql(dot)org] On Behalf Of Kris Jurka
> Sent: Monday, June 11, 2007 5:04 PM
> To: Larry McGhaw
> Cc: pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] Selecting a constant question
>
>
>
> On Mon, 11 Jun 2007, Larry McGhaw wrote:
>
> > I think perhaps we have lost sight of the main issue:
> >
> > 2) libpq can properly describe the maximum internal data size of any
> > varchar column via Pqfmod
>
> SELECT cola || colb FROM tab;
Suggestion:
Return (column size of cola) + (column size of colb) in the maximum
length field.
> > 3) libpq can properly describe the maximum internal data size of any
> > numeric constant in a SQL statement via Pqfsize
>
> SELECT 3::numeric;
Suggestion:
Return sizeof (numeric(1,0)) -- after all, it's a constant here.
In the words of the great poet "Spike Lee":
'Always do the right thing.'
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2007-06-12 00:11:49 | Re: Selecting a constant question |
Previous Message | Kris Jurka | 2007-06-12 00:03:34 | Re: Selecting a constant question |