Robert Haas <robertmhaas@gmail.com> wrote:
> On Thu, Mar 12, 2015 at 9:57 AM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
>> However, there's a difference between making a query silently given
>> different results, and breaking it completely forcing the user to
>> re-study how to write it. I think the latter is better. In that light
>> we should just drop attnum as a column name, and use something else:
>> maybe (attidnum, attlognum, attphysnum). So all queries in the wild
>> would be forced to be updated, but we would not silently change
>> semantics instead.
>
> +1 for that approach. Much better to break all of the third-party
> code out there definitively than to bet on which attribute people are
> going to want to use most commonly.
+1
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company