Re: Naming conventions for column names

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sachin Kotwal <kotsachin(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Naming conventions for column names
Date: 2017-11-06 14:33:50
Message-ID: 9696.1509978830@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Sachin Kotwal <kotsachin(at)gmail(dot)com> writes:
> I can understand that it is important to maintain naming pattern same as
> system catalogs, but in that case we may need to redefine system catalogs
> naming conventions .

Those naming conventions are twenty-five years old, and there is an
astonishing amount of client code that would break if we ran around
changing existing system catalog column names. It's very unlikely that
any proposal to do that would even receive serious consideration.

The bar to using new naming conventions in new catalogs would be
lower, of course, but then you have to think about the confusion
factor of having different naming styles in different places.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rakesh Kumar 2017-11-06 14:51:15 Re: Naming conventions for column names
Previous Message Tom Lane 2017-11-06 14:26:17 Re: xmin increasing within a transaction block?