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
Describe the bug
When creating an entity/entities within a transaction, the returned data[].items are null instead of the created object(s). Per the documentation for creating an entity, "By default, after writing to DynamoDB, ElectroDB will format and return the record through the same process as a Get/Query". Since item mutations use the same semantics within transactions (except for terminating with commit instead of go), would think the correct behavior would be for the returned data[].items to hold the created object(s).
ElectroDB Version 2.14.1
Expected behavior data[].items for created items should hold the created objects.
Additional context
Current workaround is to get the items after they're created.
The text was updated successfully, but these errors were encountered:
Describe the bug
When creating an entity/entities within a transaction, the returned
data[].item
s arenull
instead of the created object(s). Per the documentation for creating an entity, "By default, after writing to DynamoDB, ElectroDB will format and return the record through the same process as a Get/Query". Since item mutations use the same semantics within transactions (except for terminating withcommit
instead ofgo
), would think the correct behavior would be for the returneddata[].item
s to hold the created object(s).ElectroDB Version
2.14.1
Expected behavior
data[].item
s for created items should hold the created objects.Additional context
Current workaround is to get the items after they're created.
The text was updated successfully, but these errors were encountered: