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
Encountered an issue in production: When using timestamptz to store time, during the execution of a SELECT query, performing Next() or Scan() operations on the sql.Rows object may report: expected end of input, got+00:00. After debugging the code, it was found that the data format might be "2022-11-16 05:49:05.517000 +00:00" or "2022-11-16 05:49:05 +00:00", meaning there may be a space before the timezone segment. In the database parameters, the DateStyle is confirmed to be ISO, YMD.
This issue was discovered on the TBase implementation of the PostgreSQL-like database.
The text was updated successfully, but these errors were encountered:
Encountered an issue in production: When using
timestamptz
to store time, during the execution of aSELECT
query, performingNext()
orScan()
operations on thesql.Rows
object may report:expected end of input, got+00:00
. After debugging the code, it was found that the data format might be "2022-11-16 05:49:05.517000 +00:00" or "2022-11-16 05:49:05 +00:00", meaning there may be a space before the timezone segment. In the database parameters, theDateStyle
is confirmed to beISO, YMD
.This issue was discovered on the TBase implementation of the PostgreSQL-like database.
The text was updated successfully, but these errors were encountered: