DateStyle config variable

Started by Guillaume Lelargeover 19 years ago3 messagesdocs
Jump to latest
#1Guillaume Lelarge
guillaume@lelarge.info

Hi all,

I wondered if there was a reason for the mixed case capitalization of
the DateStyle setting ? all other settings are in lowercase. Even
DateStyle is in lowercase in the postgresql.conf file.

If there's none, here is a patch (CVS HEAD) to put it in lowercase.

Regards.

--
Guillaume.
<!-- http://abs.traduc.org/
http://lfs.traduc.org/
http://docs.postgresqlfr.org/ -->

#2Guillaume Lelarge
guillaume@lelarge.info
In reply to: Guillaume Lelarge (#1)
Re: DateStyle config variable

Guillaume Lelarge a �crit :

I wondered if there was a reason for the mixed case capitalization of
the DateStyle setting ? all other settings are in lowercase. Even
DateStyle is in lowercase in the postgresql.conf file.

If there's none, here is a patch (CVS HEAD) to put it in lowercase.

Sorry, I forgot to add the patch... :-/

Regards.

--
Guillaume.
<!-- http://abs.traduc.org/
http://lfs.traduc.org/
http://docs.postgresqlfr.org/ -->

Attachments:

datestyle.patchtext/plain; name=datestyle.patchDownload+14-14
#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: Guillaume Lelarge (#2)
Re: DateStyle config variable

Guillaume Lelarge <guillaume@lelarge.info> writes:

I wondered if there was a reason for the mixed case capitalization of
the DateStyle setting ? all other settings are in lowercase. Even
DateStyle is in lowercase in the postgresql.conf file.

DateStyle and TimeZone have both historically been spelled like that,
and are delivered to client code in that form (not only in SHOW but
in the lower-level ParameterStatus message). I think the odds of
breaking client-side code are very high if we change it.

regards, tom lane