| From: | Muhammad Ikram <mmikram(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Column data type in doc example may be changed to VARCHAR from TEXT |
| Date: | 2024-07-18 05:22:04 |
| Message-ID: | CAGeimVo_GGnFNv9GZS17eqMah0+aenGqHzr3+8uROVM4k5a=Vw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Thanks David for clarifying. I am coming from an Oracle background, so
there we(developers) mostly use CHAR or VARCHAR2 data types for such
identifiers instead of CLOB.
Sorry for my naiveness about PostgreSQL doc practices.
Regards,
Muhammad Ikram
Bitnine global.
On Thu, Jul 18, 2024 at 10:17 AM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Wednesday, July 17, 2024, Muhammad Ikram <mmikram(at)gmail(dot)com> wrote:
>
>>
>>
>> IMHO, a minor issue in the doc. As a good practice we use TEXT data type
>> when we expect longer text e.g. comments, doc kind of columns.
>>
>
> Who is we in this conversation? If it’s the documentation please
> reference existing work. Text is our preferred type and we are fairly
> consistent in using it to my knowledge.
>
> David J.
>
--
Muhammad Ikram
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-07-18 05:28:02 | Re: Column data type in doc example may be changed to VARCHAR from TEXT |
| Previous Message | Tom Lane | 2024-07-18 05:18:12 | Re: A minor bug in doc. Hovering over heading shows # besides it. |