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 working with the shell command, it'd be nice to get a transaction hash in the response after a mutating query is made. For example, the following query is invalid for a table t_31337_2 with schema i int, v text:
insert into t_31337_2 values (1, 0xf95980ee414ff1b68d66421500d4779b6d453c5e);
However, the information logged is simply:
{"updatedTable":"t_31337_2"}
When I go to query the table, there is no data (as expected), but I have no clue why since I do not have the txn hash.
Details
There are a couple of options. You could choose to add the txn hash to the mutation response where the information logged could be:
Alternatively, you could choose to not log a misleading updatedTable (since it wasn't updated), catch the error, and then log it on the spot (and include the txn hash, too).
Summary
When working with the
shell
command, it'd be nice to get a transaction hash in the response after a mutating query is made. For example, the following query is invalid for a tablet_31337_2
with schemai int, v text
:However, the information logged is simply:
When I go to query the table, there is no data (as expected), but I have no clue why since I do not have the txn hash.
Details
There are a couple of options. You could choose to add the txn hash to the mutation response where the information logged could be:
Alternatively, you could choose to not log a misleading
updatedTable
(since it wasn't updated), catch the error, and then log it on the spot (and include the txn hash, too).See original issue here.
From SyncLinear.com | TABJS-13
The text was updated successfully, but these errors were encountered: