Re: Selecting a constant question

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Larry McGhaw <lmcghaw(at)connx(dot)com>
Cc: Hannu Krosing <hannu(at)skype(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Dann Corbit <DCorbit(at)connx(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Selecting a constant question
Date: 2007-06-12 11:49:51
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Larry McGhaw wrote:
> Again, the issue is not our tool, but the deficiency in libpq/postgres
> ... even mysql gets its right .. why not Postgres?
> Its not hard for a database to report metadata properly.
> if I issue a sql statement:
> select '123' from <any table>
> the database should report that the maximum length of the 1st column
> in the resultset is 3 ... it cant be any more plain than that.

Making assertions like this does not make your case for you. If you
think it's that easy then send in a patch. I suspect that doing what you
want in the cases where it could be supported would require a protocol
change, with possibly an extra field in the RowDescription object. If
that's true you'd need to make a very good and compelling case indeed
for such a change. If this is so vital I'm curious to know why driver
authors haven't been screaming about it until now. I'm not dismissing
what you want, but just waving your hand and saying "it's not hard"
really won't do.



In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Zdenek Kotala 2007-06-12 12:53:25 Re: Command tags in create/drop scripts
Previous Message Martijn van Oosterhout 2007-06-12 11:43:47 Re: Selecting a constant question