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
When I create a record in a REQUEST_TX_COMMIT operation and the record gets created with a version > 0, then the generated RID of the new record appears in both the "created" and "updated" list in the response.
For example, if I create a record like this:
{
rid: #-1:-2,
fields: {a: 1},
}
the response of REQUEST_TX_COMMIT will be something like:
1, // count of created records
#-1:-2, // client rid
#9:0, // server rid
1, // count of updated records
#-1:-2, // server rid
1, // version
...
to solve this, i need to update the protocol or unsure that the create has every time version 0 as result, i'll check the version force as first solution so it will avoid to change the binary protocol
When I create a record in a
REQUEST_TX_COMMIT
operation and the record gets created with a version > 0, then the generated RID of the new record appears in both the "created" and "updated" list in the response.For example, if I create a record like this:
the response of
REQUEST_TX_COMMIT
will be something like:/cc @tglman
The text was updated successfully, but these errors were encountered: