From: | Przemysław Sztoch <przemyslaw(at)sztoch(dot)pl> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: date_trunc function in interval version |
Date: | 2023-12-22 22:25:51 |
Message-ID: | 922c8f8e-859b-6278-f399-46a7e19ab4b2@sztoch.pl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
In my opinion date_trunc is very good name.
Truncated data is timestamp type, not interval.
First parameter has same meaning in original date_trunc and in my new
version.
New version provides only more granularity.
Pavel Stehule wrote on 12/22/2023 8:43 PM:
> Hi
>
> pá 22. 12. 2023 v 20:26 odesílatel Przemysław Sztoch
> <przemyslaw(at)sztoch(dot)pl <mailto:przemyslaw(at)sztoch(dot)pl>> napsal:
>
> Hello.
> There is date_trunc(interval, timestamptz, timezone) function.
> First parameter can be '5 year', '2 month', '6 hour', '3 hour',
> '15 minute', '10 second' etc.
>
>
> should not be named interval_trunc instead? In this case the good name
> can be hard to choose, but with the name date_trunc it can be hard to
> find it.
>
> Regards
>
> Pavel
>
> --
> Przemysław Sztoch | Mobile +48 509 99 00 66
>
--
Przemysław Sztoch | Mobile +48 509 99 00 66
From | Date | Subject | |
---|---|---|---|
Next Message | Chen Hao Hsu | 2023-12-22 23:18:16 | Fixing pgbench init overflow |
Previous Message | Tom Lane | 2023-12-22 22:11:36 | Re: authentication/t/001_password.pl trashes ~/.psql_history |