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
For findAndModify with upsert, we run the update object against parseInsertObj since we might be inserting a new document. However, we may also just be doing an update, and the current implementation will always replace the createdAt and updatedAt fields, meaning createdAt gets overwritten. Will add a small fix not to overwrite createdAt.
We also have the scenario where we replace whatever updatedAt field we were passed. However, I believe we can count this situation as intended behavior. Thoughts @dimensia?
The text was updated successfully, but these errors were encountered:
For
findAndModify
withupsert
, we run the update object againstparseInsertObj
since we might be inserting a new document. However, we may also just be doing an update, and the current implementation will always replace thecreatedAt
andupdatedAt
fields, meaningcreatedAt
gets overwritten. Will add a small fix not to overwritecreatedAt
.We also have the scenario where we replace whatever
updatedAt
field we were passed. However, I believe we can count this situation as intended behavior. Thoughts @dimensia?The text was updated successfully, but these errors were encountered: