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
In MongoDB with Mongoose, you do not need to manually create a createdAt field if you're using Mongoose's built-in timestamps option. This option automatically adds createdAt and updatedAt fields to your schema.
By setting the timestamps option to true in the schema, Mongoose will automatically handle the createdAt and updatedAt fields for you.
At backend/src/models/coreModels, backend/src/models/appModels/Client.js, backend/src/controllers/appControllers/clientController/summary.js, backend/src/models/appModels/Invoice.js, backend/src/models/appModels/Payment.js, backend/src/models/appModels/PaymentMode.js, backend/src/models/appModels/Quote.js, backend/src/models/appModels/Taxes.js, backend/src/models/coreModels/Admin.js , backend/src/models/coreModels/Upload.js we can see the explicit declaration of created field.
We shall use timestamp boolean instead.
The text was updated successfully, but these errors were encountered:
In MongoDB with Mongoose, you do not need to manually create a createdAt field if you're using Mongoose's built-in timestamps option. This option automatically adds createdAt and updatedAt fields to your schema.
By setting the timestamps option to true in the schema, Mongoose will automatically handle the createdAt and updatedAt fields for you.
At
backend/src/models/coreModels
,backend/src/models/appModels/Client.js
,backend/src/controllers/appControllers/clientController/summary.js
,backend/src/models/appModels/Invoice.js
,backend/src/models/appModels/Payment.js
,backend/src/models/appModels/PaymentMode.js
,backend/src/models/appModels/Quote.js
,backend/src/models/appModels/Taxes.js
,backend/src/models/coreModels/Admin.js
,backend/src/models/coreModels/Upload.js
we can see the explicit declaration ofcreated
field.We shall use timestamp boolean instead.
The text was updated successfully, but these errors were encountered: