-
Notifications
You must be signed in to change notification settings - Fork 466
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support timetz datatype #2982
Comments
This feature is available in the v2.1.0-alpha.20170507 release. @rmloveland, I might try to get it documented in time. |
Also minor tweaks to the TIMEZONE type docs. Fixes #2982
Cockroach PR that introduced (for reference): |
Fixes #2982 Summary of changes: - Make clear that TIMETZ is not really recommended, just there for SQL standard and ORM support (2.1) - Give examples of wonkiness: comparisons and ordering (2.1) - Update SQL Feature page with TIME data type (2.0 and 2.1) - Update example to use TIME, not TIMETZ - Add links to other related docs as appropriate: Postgres time stuff and wire protocol, Cockroach SQL feature page and functions/operators - Fixed a few small typos/copy-edits - Also minor tweaks to the TIMEZONE type docs
Fixes #2982 Summary of changes: - Make clear that TIMETZ is not really recommended, just there for SQL standard and ORM support (2.1) - Give examples of wonkiness: comparisons and ordering (2.1) - Update SQL Feature page with TIME data type (2.0 and 2.1) - Update example to use TIME, not TIMETZ - Add links to other related docs as appropriate: Postgres time stuff and wire protocol, Cockroach SQL feature page and functions/operators - Fixed a few small typos/copy-edits - Also minor tweaks to the TIMEZONE type docs
Based on #3254, It's unclear what will happen with this type (cockroachdb/cockroach#25224), so reopening this issue for now. |
@rmloveland, based on the updated roadmap, we're going to hide this feature in 2.1. The remaining docs work, therefore, is just to remove mention of timetz from the docs. |
From first 2.1 beta:
|
Doc impact:
|
Background: https://airtable.com/tblD3oZPLJgGhCmch/viw8IfZMg9Up8SP33/recgAULbWY1898miw
PM: @awoods187
Eng Partner:
The text was updated successfully, but these errors were encountered: