You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can get this error: Query Error: error occurred while decoding column \"col\": mismatched types; Rust type core::option::Option<chrono::datetime::DateTime<chrono::offset::utc::Utc>> (as SQL type TIMESTAMPTZ) is not compatible with SQL type TIMESTAMP
On PostgresQL, TIMESTAMP is the same as DATETIME. col, which is with Timestamp column type, should be decoded as the same as DateTime.
However the current behaviour should be kept when using with MySQL.
The text was updated successfully, but these errors were encountered:
I see, but sadly in Entity definition there is no way to know whether it is MySQL or Postgres. MySQL does not have timestamptz. But I do think we can specifically convert Timestamp to DateTime<Utc> on the MySQL connector (it's the same data with a different type hint, afterall).
PR would be appreciated.
xtexChooser
added a commit
to xtexChooser/central
that referenced
this issue
May 3, 2024
As the document:
DateTimeUtc
should be regarded as Timestamp, however, it is regarded as TimestampWithTimeZoneFrom the following Model:
I can get this error:
Query Error: error occurred while decoding column \"col\": mismatched types; Rust type core::option::Option<chrono::datetime::DateTime<chrono::offset::utc::Utc>> (as SQL type TIMESTAMPTZ) is not compatible with SQL type TIMESTAMP
On PostgresQL, TIMESTAMP is the same as DATETIME.
col
, which is with Timestamp column type, should be decoded as the same asDateTime
.However the current behaviour should be kept when using with MySQL.
The text was updated successfully, but these errors were encountered: