Date: Wed, 29 Apr 2020 12:29:28 +1000
From: raf <raf@raf.org>
To: pgsql-admin@lists.postgresql.org
Subject: Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length)
Message-ID: <20200429022928.fywdmiuc6oqpmgtc@raf.org>
References: 
 <CAOasRJYCUwMYdd=BL29TupW_iCbvM3YRM01YTB_WYSUEays3CA@mail.gmail.com>
 <CAKhGwmB_C4a1XVrzYsr3CFmUxegZyvsC=7QtzkW6TP27J5G31w@mail.gmail.com>
 <20200428234332.7nkyomr2unlez6p5@raf.org>
 <8EC9D082-B541-435F-9EE3-3ED14AA3C2D1@crazybean.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <8EC9D082-B541-435F-9EE3-3ED14AA3C2D1@crazybean.net>
Precedence: bulk

Rui DeSousa wrote:

> > On Apr 28, 2020, at 7:43 PM, raf <raf@raf.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