public inbox for [email protected]
help / color / mirror / Atom feedFrom: Vladimir Sitnikov <[email protected]>
To: Dave Cramer <[email protected]>
Cc: Manav Kumar <[email protected]>
Cc: [email protected]
Cc: Laurenz Albe <[email protected]>
Subject: Re: Understanding DateStyle guc in startup packet
Date: Mon, 19 May 2025 18:37:24 +0300
Message-ID: <CAB=Je-EmfXoyBRm2LefkxugqNGPta7vf=Ky8ycYpkd02_-WX_w@mail.gmail.com> (raw)
In-Reply-To: <CADK3HHKC-1iTEZNT4fvjS-mBkLYVmKQVG3Kvq9_KHXnctACUjA@mail.gmail.com>
References: <CAPhCW+-oyivUiBiP5nOMQNxQzXLnT62SvCZ1oq7rqZkHq34KGA@mail.gmail.com>
<CAB=Je-Gznb3j_M--EAn9zW0cHLzgMg_YyWxWGM==g_kRfxEzrA@mail.gmail.com>
<CADK3HHKC-1iTEZNT4fvjS-mBkLYVmKQVG3Kvq9_KHXnctACUjA@mail.gmail.com>
>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.
Vladimir
view thread (7+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Understanding DateStyle guc in startup packet
In-Reply-To: <CAB=Je-EmfXoyBRm2LefkxugqNGPta7vf=Ky8ycYpkd02_-WX_w@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox