| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | harry(at)harryclarke(dot)me(dot)uk, PostgreSQL Documentation <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: text and varchar are not equivalent |
| Date: | 2024-02-09 17:24:19 |
| Message-ID: | CAKFQuwbUeWu8fp5J1FW2vBn8-5RGnVS+Jtdri38HJbYT+VLPmA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Fri, Feb 9, 2024, 10:12 PG Doc comments form <noreply(at)postgresql(dot)org>
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/16/datatype-character.html
> Description:
>
> The documentation implies that the data types text and varchar are
> equivalent, but this is not the case with this test in Postgresql version
> 16.
>
Fair point. But I'd rather further emphasize that char should just be
avoided so this and other unexpected outcomes simply do not manifest in a
real database scenario. Rather than try and document how odd it's behavior
is when dealing with intra-textual type conversions.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-02-09 17:51:51 | Re: text and varchar are not equivalent |
| Previous Message | PG Doc comments form | 2024-02-09 11:18:22 | text and varchar are not equivalent |