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
Cloud Spanner has two execution modes for DML, DML and Partitioned DML, but currently spanner-cli only supports normal DML. It would be better to support Partitioned DML in spanner-cli since it can process large-scale operations over the entire rows.
One thing we might need to discuss would be syntax for executing a Partitioned DML.
@apstndb You mentioned EXECUTE PARTITIONED (INSERT|UPDATE|DELETE) ... as an example for the syntax in #92 (comment), but what is the rationale behind it?
I'm wondering if we can make it simpler by just saying PARTITIONED (INSERT|UPDATE|DELETE) ... to indicate executing the DML as a Partitioned DML.
EXECUTE PARTITIONED (INSERT|UPDATE|DELETE) is inspired by EXECUTE IMMEDIATE but only for example and no rationale.
It may be even wrong because of ambiguous syntax with the standard Dynamic SQL(EXECUTE IMMEDIATE, PREPARE and EXECUTE).
I want to vote PARTITIONED (INSERT|UPDATE|DELETE) ... because it is simple and unambiguous.
Cloud Spanner has two execution modes for DML, DML and Partitioned DML, but currently spanner-cli only supports normal DML. It would be better to support Partitioned DML in spanner-cli since it can process large-scale operations over the entire rows.
One thing we might need to discuss would be syntax for executing a Partitioned DML.
Context: #92 (comment)
The text was updated successfully, but these errors were encountered: