| From: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
|---|---|
| To: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
| Cc: | Manav Kumar <mkumar(at)yugabyte(dot)com>, pgsql-jdbc(at)lists(dot)postgresql(dot)org, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Subject: | Re: Understanding DateStyle guc in startup packet |
| Date: | 2025-05-19 17:25:54 |
| Message-ID: | CADK3HHJCnx6Y7Dijmu+XkAqATmYGnGNuvLsc3i5BxsUzZjVX_Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Mon, 19 May 2025 at 11:43, Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
wrote:
> >Why would you want to change it?
>
> Applications might have their own view on the way DateStyle connection
> property should be set.
> It could make a difference if the app uses things like select
> '03-05-2025'::date.
>
> Of course, it would be great if the app code could resist from casting
> text to dates, however,
> I think the driver should stand in the way there by enforcing a very
> specific DateStyle value.
>
> To me, DateStyle looks like timezone, and client_encoding which we
> currently enforce, yet we could do better and skip enforcing the values.
>
If the JDK supports all the variants then yes we could easily accomplish
this.
Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manav Kumar | 2025-05-23 08:38:07 | Re: Understanding DateStyle guc in startup packet |
| Previous Message | Vladimir Sitnikov | 2025-05-19 15:37:24 | Re: Understanding DateStyle guc in startup packet |