How do I run the party_statuses commands from the shell?

Reads one page of the collection. Nothing addresses it but the caller's tenant, so it is the read that shows what exists.

The command is shaped like this:

party_statuses list [--offset <n>] [--limit <n>] [--order <field>] [--desc]

It is addressed at refdata.v1.party_statuses.list.

party_statuses list --limit 1

Reads the one row its key addresses. A key states every identifying column, so a partial key is refused rather than answered with an arbitrary row.

The command is shaped like this:

party_statuses get <code>

It is addressed at refdata.v1.party_statuses.get.

party_statuses get __none__

Reads several rows in one request, one key group per row.

The command is shaped like this:

party_statuses get-many <code>

It is addressed at refdata.v1.party_statuses.get_many.

party_statuses get-many __none__

Writes a row. The change states that the row must not exist, so a create that collides with an existing row is refused rather than replacing it. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved.

The command is shaped like this:

party_statuses add <code> <name> <description> <display_order> <reason> <commentary>

It is addressed at refdata.v1.party_statuses.put.

party_statuses add __none__ __none__ __none__ 0 system.new_record generated_script

Writes a row. The change states no precondition, so it replaces whatever row the key already addresses. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved. Passing –version makes the write conditional on the version the caller last read.

The command is shaped like this:

party_statuses set <code> <name> <description> <display_order> <reason> <commentary> [--version <n>]

It is addressed at refdata.v1.party_statuses.put.

party_statuses set __none__ __none__ __none__ 0 system.new_record generated_script

Writes several rows in one request. The count states how many field groups follow. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved.

The command is shaped like this:

party_statuses put-many --count <n> <code> <name> <description> <display_order> <reason> <commentary>

It is addressed at refdata.v1.party_statuses.put_many.

party_statuses put-many --count 1 __none__ __none__ __none__ 0 system.new_record generated_script

Removes a row. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved. Passing –version makes the write conditional on the version the caller last read.

The command is shaped like this:

party_statuses delete <code> <reason> <commentary> [--version <n>]

It is addressed at refdata.v1.party_statuses.delete.

party_statuses delete __none__ system.new_record generated_script

Removes several rows in one request. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved.

The command is shaped like this:

party_statuses delete-many <code> <reason> <commentary>

It is addressed at refdata.v1.party_statuses.delete_many.

party_statuses delete-many __none__ system.new_record generated_script

Reads the row's recorded history, newest first.

The command is shaped like this:

party_statuses versions <code> [--offset <n>] [--limit <n>] [--order <field>] [--desc]

It is addressed at refdata.v1.party_statuses_versions.list.

party_statuses versions __none__ --limit 1

Reads one recorded version of the row.

The command is shaped like this:

party_statuses version <code> --version <n>

It is addressed at refdata.v1.party_statuses_versions.get.

party_statuses version __none__ --version 1