| From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | Larry McGhaw <lmcghaw(at)connx(dot)com> |
| Cc: | 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 08:06:58 |
| Message-ID: | 466E5422.5010300@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Larry McGhaw wrote:
> Again, *all* other major relational databases do this ... even blob fields have a maximum length reported from the database.
So what are you doing with the max length? Not all data types and values
have a meaningful max length, so you have to be able to deal with
variable length data anyway.
For blobs, exactly what max length would you like to get; 1GB? 1TB? Why,
what good is that for?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ITAGAKI Takahiro | 2007-06-12 08:35:55 | Re: Autovacuum launcher doesn't notice death of postmaster immediately |
| Previous Message | Magnus Hagander | 2007-06-12 08:03:40 | Re: ecpg compile error in regression tests |