| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Eduardo Pérez Ureta <edpeur(at)gmail(dot)com> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14841: Remove TIME WITH TIME ZONE type |
| Date: | 2017-10-03 21:42:57 |
| Message-ID: | CAKFQuwaOU51pZRAfjoqKFWsm7+JdyM4OE8RCjvLRwOJnN+r+eQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Oct 3, 2017 at 2:19 PM, Eduardo Pérez Ureta <edpeur(at)gmail(dot)com>
wrote:
> Of course, this fix will not need to be included in any current supported
> release.
> But, would you remove the TIME WITH TIME ZONE type in a new major release?
>
> What is the priority for PostgreSQL, standards conformance, or making a
> useful product without broken features?
>
In this case neither - the priority here is not breaking people's working
applications when they upgrade from one major release to the next (and
minimizing the amount of pain involved when migrating from other
SQL-standard compliant databases to ours).
The SO post isn't even a question from someone being tricked/confused into
using "timetz" but rather a intellectual exercise into why it exists.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2017-10-03 21:54:34 | Re: BUG #14842: TIMESTAMP WITH TIME ZONE and TIMESTAMP WITHOUT TIMEZONE should not be comparable |
| Previous Message | Eduardo Pérez Ureta | 2017-10-03 21:19:46 | Re: BUG #14842: TIMESTAMP WITH TIME ZONE and TIMESTAMP WITHOUT TIMEZONE should not be comparable |