Re: Prepping to break every past release... - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Prepping to break every past release...
Date
Msg-id 1236200616.18420.53.camel@jd-laptop.pragmaticzealot.org
Whole thread Raw
In response to Re: Prepping to break every past release...  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Prepping to break every past release...  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On Wed, 2009-03-04 at 15:50 -0500, Andrew Dunstan wrote:

> > It seems to me that the best method would be to follow the
> > information_schema naming conventions as information_schema is standard
> > compliant (right?).
> >
> > Thoughts?
> >   
> 
> 
> What would be the benefit? Apart from satisfying a passion for consistency?

It would lower the cost (intellectually as well as dollars) of
development and administration for every single user of the database.

I can't count how many times I accidentally type tablename versus
table_name or worse relname, etc... 

Sincerely,

Joshua D. Drake





-- 
PostgreSQL - XMPP: jdrake@jabber.postgresql.org  Consulting, Development, Support, Training  503-667-4564 -
http://www.commandprompt.com/ The PostgreSQL Company, serving since 1997
 



pgsql-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: Prepping to break every past release...
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Prepping to break every past release...