From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: How to do faster DML |
Date: | 2024-02-12 20:30:52 |
Message-ID: | CANzqJaDxd7JuH5hHY37or8pLYN-h2982xZ0xcBBO8Do5UW6__w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Feb 12, 2024 at 3:23 PM veem v <veema0000(at)gmail(dot)com> wrote:
[snip]
> So it looks like the fixed length data type(like integer, float) should be
> the first choice while choosing the data type of the attributes
> wherever possible, as these are native types.
>
Correct.
> (Like choosing "Integer/float" over "Numeric", "Char" over "Varchar" etc).
>
However I do see even in Oracle databases, we have Integer type too, but
> it's suggesting(For e.g. in below blog) to rather go with Number types over
> Integer and Varchar2 over Char, which is opposite of what we are discussing
> here. Is the fixed length data type behaves differently in postgres vs
> oracle and thus should be treated differently?
>
> https://www.databasestar.com/oracle-data-types/
>
>
> From above blog:-
>
Oracle is not Postgresql. WTH are you using an Oracle blog to decide on
Postgresql data types????
>
>
> *When to use CHAR: There should be no reason to use the CHAR data type, as
> it is similar to a VARCHAR2 and it’s better to be consistent.*
> *When to use INTEGER: You should use the NUMBER data type instead.*
>
>
Did you actually read that blog post?
Have you even read the Postgresql documentation on data types?
From | Date | Subject | |
---|---|---|---|
Next Message | veem v | 2024-02-12 20:43:12 | Re: How to do faster DML |
Previous Message | veem v | 2024-02-12 20:23:25 | Re: How to do faster DML |