Dear Moderators,
with this approach, why don't you eliminate char and varchar then ?
Thanks for thinking over.
BR
Grega
-Original Message-
From: Laurenz Albe
Sent: Saturday, November 6, 2021 6:28 AM
To: Bruce Momjian ; David G. Johnston
Cc: Grega Jesih ; Tom Lane ; Pg
Docs
Su
record.
Optional additional remark:
Another good aspect of known data sizes is easier understanding of field
content and implicit data (length) control.
Best regards
Grega
From: David G. Johnston
Sent: Thursday, November 4, 2021 2:51 PM
To: Grega Jesih
Cc: Tom Lane ; Pg Docs
Subject: Re: text fiel
h-method-when-dealing-with-source-lob-columns
If this contribution from stackexchange isn't enough, let me know.
BR
Grega
From: David G. Johnston
Sent: Wednesday, November 3, 2021 7:40 PM
To: Grega Jesih
Cc: Tom Lane ; grega.je...@gmail.com; Pg Docs
Subject: Re: text fields and perfo
f a database model where for a currency of true
size 3 you choose char(3) instead of text.
You prevent a dummy insert on a database level. So no text len>3 may enter this
field.
BR
Grega
Od: Tom Lane
Poslano: 3. november 2021 18:37:28
Za: Grega Jesih
Kp
Dear David,
> The goal in our docs is to point out that using an arbitrary length
> specification is not required in PostgreSQL.
Then it should say so. Because unexperienced reader then uses this limited
focus and generalizes.
It is for the very same reason that progreammers don't perceive the n
