| From: | raf <raf(at)raf(dot)org> |
|---|---|
| To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length) |
| Date: | 2020-04-29 02:29:28 |
| Message-ID: | 20200429022928.fywdmiuc6oqpmgtc@raf.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Rui DeSousa wrote:
> > On Apr 28, 2020, at 7:43 PM, raf <raf(at)raf(dot)org> wrote:
> >
> > I just use "text" for everything. It's less typing. :-)
>
> Ugh, I see it as sign that the designers of the schema didn’t fully
> think about the actual requirements or care about them and it usually
> shows.
You are mistaken. I care a lot. That's why I
future-proof designs whenever possible by
not imposing arbitrarily chosen limits that
appear to suit current requirements.
In other words, I know I'm not smart enough
to predict the future so I don't let that
fact ruin my software. :-)
cheers,
raf
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rui DeSousa | 2020-04-29 04:19:05 | Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length) |
| Previous Message | David G. Johnston | 2020-04-29 01:22:42 | Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2020-04-29 02:37:00 | Re: Pulling up sublink may break join-removal logic |
| Previous Message | Melanie Plageman | 2020-04-29 02:03:53 | Re: Avoiding hash join batch explosions with extreme skew and weird stats |