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
I know ElectroDB have a feature transaction.write().
But when using put() and delete(), we want to use BatchWriteItem because it is less cost and higher performance.
The interface will be like following:
// create a user and attach to a tenantawaitservice.batchWrite.user.put({userId: "",registrationCode: ""}).userTenantMap.put({userId: "",tenantId: ""}).registrationCode.delete({registrationCode: ""}).go()
or
// create a user and attach to a tenantawaitservice.batchWrite([service.entities.user.put({userId: "",registrationCode: ""}),service.entities.userTenantMap.put({userId: "",tenantId: ""}),service.entities.registrationCode.delete({registrationCode: ""}),]).go()
Actually, BatchWriteItem can effect to multiple table, but if following ElectroDB service concept, it is enough to provide the feature BatchWriteItem only for entities closed in service I think.
The text was updated successfully, but these errors were encountered:
I know ElectroDB have a feature
transaction.write()
.But when using
put()
anddelete()
, we want to useBatchWriteItem
because it is less cost and higher performance.The interface will be like following:
or
Actually,
BatchWriteItem
can effect to multiple table, but if following ElectroDBservice
concept, it is enough to provide the featureBatchWriteItem
only for entities closed in service I think.The text was updated successfully, but these errors were encountered: