I can’t agree more. We should be able to make changes in a manner that
improves the DB In the long term, rather than live with the technical debt
of arbitrary decisions made by a handful of people.
I also agree that putting a knob in place to let people migrate over is a
reasonable decision.
Jon
The goal is simply to agree on a set of well-defined principles for how we
should behave. If we don’t like the implications that arise, we’ll have
another vote? A democracy cannot bind itself, so I never understood this fear
of a decision.
A database also has a thousand toggles. If we absolu
On Tue, Nov 20, 2018 at 5:02 PM Benedict Elliott Smith
wrote:
> FWIW, my meaning of arithmetic in this context extends to any features we
> have already released (such as aggregates, and perhaps other built-in
> functions) that operate on the same domain. We should be consistent, after
> all.
>
> If those tickets were sitting in patch available state prior to the
freeze they *should* get in.
I assume it's obvious to everyone that this should be taken on a
case-by-case basis. There's at least 2 that were in that list (one of which
Marcus bumped off PA) that are potentially big and hairy ch
Kurt, I don't believe this should be subject of "heated debate". If those
tickets were sitting in patch available state prior to the freeze they *should*
get in.
Vinay, I can help review the tickets.
Dinesh
On Tuesday, November 20, 2018, 2:59:18 PM PST, kurt greaves
wrote:
Thanks Vin
