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
We are trying to duplicate records and we want to preserve the original createdAt. Right now it seems that passing createdAt as a field will not force that value and it will automatically use current creation date.
It works if we perform an update on the newly created record, but we'de prefer not having to perform 2 queries on 1000s of records.
Is there a way around that to overwrite the automatically set createdAt on creation?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are trying to duplicate records and we want to preserve the original createdAt. Right now it seems that passing createdAt as a field will not force that value and it will automatically use current creation date.
It works if we perform an update on the newly created record, but we'de prefer not having to perform 2 queries on 1000s of records.
Is there a way around that to overwrite the automatically set createdAt on creation?
Beta Was this translation helpful? Give feedback.
All reactions