Support Timestamptz
#106
Comments
|
Any implementation which tackles this should likely handle https://github.com/sgrif/diesel/blob/c26d299da9b4b3e71b545c74dbc95ae13b2bbb98/diesel/src/expression/date_and_time.rs#L23 as well. |
sgrif
added a commit
that referenced
this issue
Aug 18, 2016
This adds support for the `timestamp with time zone` type. This is part of the SQL standard, but not supported explicitly by SQLite as far as I can tell. As such I've made it a PG specific type for now. timestamp with time zone does not actually mean that a time zone is stored. It instead means that when dealing with strings, Postgres will no longer ignore the time zone portion. It will convert the time zone to UTC for storage. When transmitted as text, it will be converted to the database's local time zone. When transmitted as binary, it will be sent as UTC. As such, I've provided `ToSql` implementations for basically all flavors of `DateTime`, but I've only provided a `FromSql` implementation for `DateTime<UTC>` and `NaiveDateTime`. I have not provided any implementation for `std::time::SystemTime`, as it implies local time zone for the machine and we do not have the tools to handle the conversion in the standard library. Fixes #106. Fixes #295. Fixes #402.
sgrif
added a commit
that referenced
this issue
Aug 18, 2016
This adds support for the `timestamp with time zone` type. This is part of the SQL standard, but not supported explicitly by SQLite as far as I can tell. As such I've made it a PG specific type for now. timestamp with time zone does not actually mean that a time zone is stored. It instead means that when dealing with strings, Postgres will no longer ignore the time zone portion. It will convert the time zone to UTC for storage. When transmitted as text, it will be converted to the database's local time zone. When transmitted as binary, it will be sent as UTC. As such, I've provided `ToSql` implementations for basically all flavors of `DateTime`, but I've only provided a `FromSql` implementation for `DateTime<UTC>` and `NaiveDateTime`. I have not provided any implementation for `std::time::SystemTime`, as it implies local time zone for the machine and we do not have the tools to handle the conversion in the standard library. Fixes #106. Fixes #295. Fixes #402.
sgrif
added a commit
that referenced
this issue
Aug 18, 2016
This adds support for the `timestamp with time zone` type. This is part of the SQL standard, but not supported explicitly by SQLite as far as I can tell. As such I've made it a PG specific type for now. timestamp with time zone does not actually mean that a time zone is stored. It instead means that when dealing with strings, Postgres will no longer ignore the time zone portion. It will convert the time zone to UTC for storage. When transmitted as text, it will be converted to the database's local time zone. When transmitted as binary, it will be sent as UTC. As such, I've provided `ToSql` implementations for basically all flavors of `DateTime`, but I've only provided a `FromSql` implementation for `DateTime<UTC>` and `NaiveDateTime`. I have not provided any implementation for `std::time::SystemTime`, as it implies local time zone for the machine and we do not have the tools to handle the conversion in the standard library. Fixes #106. Fixes #295. Fixes #402.
sgrif
added a commit
that referenced
this issue
Aug 18, 2016
This adds support for the `timestamp with time zone` type. This is part of the SQL standard, but not supported explicitly by SQLite as far as I can tell. As such I've made it a PG specific type for now. timestamp with time zone does not actually mean that a time zone is stored. It instead means that when dealing with strings, Postgres will no longer ignore the time zone portion. It will convert the time zone to UTC for storage. When transmitted as text, it will be converted to the database's local time zone. When transmitted as binary, it will be sent as UTC. As such, I've provided `ToSql` implementations for basically all flavors of `DateTime`, but I've only provided a `FromSql` implementation for `DateTime<UTC>` and `NaiveDateTime`. I have not provided any implementation for `std::time::SystemTime`, as it implies local time zone for the machine and we do not have the tools to handle the conversion in the standard library. Fixes #106. Fixes #295. Fixes #402.
|
Please show how to use this Timestamptz. I am having error infer_schema on db for timestamp pg fields. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This should be separate from
Timestamp. To start I would like to be incredibly conservative about any comparisons with these types, and not treattimestampandtimestamptzas interchangeable. I'm not super well versed in the semantics of this type -- it does sound like it mostly ends up being UTC on the backend, so we might be able to loosen this later.The text was updated successfully, but these errors were encountered: