| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Sachin Kotwal <kotsachin(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-07 15:41:09 |
| Message-ID: | 20171107154109.2bpg34u64ymdp4ug@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Sachin Kotwal wrote:
> 3. Notify or highlight these changes in release notes because this can
> break some existing tools and user code.
Notifying people when their tools no longer work with a new server is
not the problem; they figure that out pretty quickly once they try the
new version. The problem is that if you change any names, the
application developers need to provide version-specific queries that
work across all the PG versions they want to support. That leads to
some pretty horrible code, annoyed developers, bad publicity for Pg
("you guys don't love your app developers!"), etc.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2017-11-07 16:09:49 | Re: idle in transaction, why |
| Previous Message | Tom Lane | 2017-11-07 15:27:45 | Re: Block duplications in a shared buffers |