BUG #14841: Remove TIME WITH TIME ZONE type
The following bug has been logged on the website:
Bug reference: 14841
Logged by: Eduardo Perez
Email address: edpeur@gmail.com
PostgreSQL version: Unsupported/Unknown
Operating system: All
Description:
Please, remove support for the TIME WITH TIME ZONE type as there are no
valid use cases for it and being available only calls for its misuse. By
removing it you may allow people to fix their applications.
https://dba.stackexchange.com/questions/187351/what-is-a-valid-use-case-for-using-time-with-time-zone
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Tue, Oct 3, 2017 at 12:35 PM, <edpeur@gmail.com> wrote:
The following bug has been logged on the website:
Bug reference: 14841
Logged by: Eduardo Perez
Email address: edpeur@gmail.com
PostgreSQL version: Unsupported/Unknown
Operating system: All
Description:Please, remove support for the TIME WITH TIME ZONE type as there are no
valid use cases for it and being available only calls for its misuse. By
removing it you may allow people to fix their applications.
https://dba.stackexchange.com/questions/187351/what-is-a-
valid-use-case-for-using-time-with-time-zone
Actually, removing it would FORCE people to fix their applications; people
are already allowed to fix their own applications.
In any case this isn't a bug report - the software is working exactly as
designed and, furthermore, to the letter of the specification to which it
attempts to conform.
The only thing I'd consider, if I felt mis-use of this was pervasive, would
be converting the plain sentence on this topic to a callout "Note" to
emphasize the risk. The risk of making standard-conforming theoretically
broken applications actually broken outweighs removing a marginal foot-gun.
David J.
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?
2017-10-03 19:50 GMT+00:00 David G. Johnston <david.g.johnston@gmail.com>:
Show quoted text
On Tue, Oct 3, 2017 at 12:35 PM, <edpeur@gmail.com> wrote:
The following bug has been logged on the website:
Bug reference: 14841
Logged by: Eduardo Perez
Email address: edpeur@gmail.com
PostgreSQL version: Unsupported/Unknown
Operating system: All
Description:Please, remove support for the TIME WITH TIME ZONE type as there are no
valid use cases for it and being available only calls for its misuse. By
removing it you may allow people to fix their applications.
https://dba.stackexchange.com/questions/187351/what-is-a-val
id-use-case-for-using-time-with-time-zoneActually, removing it would FORCE people to fix their applications;
people are already allowed to fix their own applications.In any case this isn't a bug report - the software is working exactly as
designed and, furthermore, to the letter of the specification to which it
attempts to conform.The only thing I'd consider, if I felt mis-use of this was pervasive,
would be converting the plain sentence on this topic to a callout "Note" to
emphasize the risk. The risk of making standard-conforming theoretically
broken applications actually broken outweighs removing a marginal foot-gun.David J.
On Tue, Oct 3, 2017 at 2:19 PM, Eduardo Pérez Ureta <edpeur@gmail.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.