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
{{ message }}
This repository has been archived by the owner on May 18, 2024. It is now read-only.
When defining datetime column, time zone is very important when considering global service. However, default datetime columns like CreateDateColumn or DeleteDateColumn of typeorm does not archive the time zone when using postgres database. Furthermore, typeorm does not archive milliseconds.
I think it's a critical mistake of typeorm, but they think it's not a bug but spec.
Therefore, let safe-typeorm to support custom creation timestamp columns which support time zone and milliseconds.
The text was updated successfully, but these errors were encountered:
When defining datetime column, time zone is very important when considering global service. However, default datetime columns like
CreateDateColumn
orDeleteDateColumn
oftypeorm
does not archive the time zone when usingpostgres
database. Furthermore,typeorm
does not archive milliseconds.I think it's a critical mistake of
typeorm
, but they think it's not a bug but spec.Therefore, let
safe-typeorm
to support custom creation timestamp columns which support time zone and milliseconds.The text was updated successfully, but these errors were encountered: