| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com> |
| Cc: | PGSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Why some GUC parameter names are not lowercased |
| Date: | 2012-10-30 16:11:38 |
| Message-ID: | 12982.1351613498@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com> writes:
> Is there a reason why Postgres chose to not use all lowercase characters
> for these parameters' names.
> DateStyle
> IntervalStyle
> TimeZone
It's historical, for sure. I think we've discussed changing them and
decided it would be more likely to break things than improve matters.
In particular, modern style would probably be more like "date_style"
etc, but we definitely could not insert underscores without breaking
applications all over the place. So the best we could do is just
smash to lowercase, eg "datestyle", which isn't really a readability
improvement. And there would still be some risk of breaking
applications that are expecting these names to print a particular way.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Seref Arikan | 2012-10-30 16:14:23 | Re: Select Query Implementation:Details needed |
| Previous Message | Gurjeet Singh | 2012-10-30 15:49:36 | Why some GUC parameter names are not lowercased |