Fix updatedAt
field initialization in gdocs_posts
#3839
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #3832
Fix the issue where
gdocs_posts.updatedAt
is often set to the Unix epoch instead ofNULL
.db/model/Gdoc/GdocFactory.ts
new Date(null)
withnull
in theupdatedAt
field initialization.updatedAt
is explicitly set toNULL
if no updates have occurred post create.db/model/Post.ts
new Date(null)
withnull
in theupdatedAt
field initialization.updatedAt
is explicitly set toNULL
if no updates have occurred post create.Todo