How do I run the benchmark_rates 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:

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

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

benchmark_rates 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:

benchmark_rates get <code> <coding_scheme_code>

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

benchmark_rates get __none__ __none__

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

The command is shaped like this:

benchmark_rates get-many <code> <coding_scheme_code>

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

benchmark_rates get-many __none__ __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:

benchmark_rates add <code> <coding_scheme_code> <source> <description> <reason> <commentary>

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

benchmark_rates add __none__ __none__ __none__ __none__ 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:

benchmark_rates set <code> <coding_scheme_code> <source> <description> <reason> <commentary> [--version <n>]

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

benchmark_rates set __none__ __none__ __none__ __none__ 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:

benchmark_rates put-many --count <n> <code> <coding_scheme_code> <source> <description> <reason> <commentary>

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

benchmark_rates put-many --count 1 __none__ __none__ __none__ __none__ 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:

benchmark_rates delete <code> <coding_scheme_code> <reason> <commentary> [--version <n>]

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

benchmark_rates delete __none__ __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:

benchmark_rates delete-many <code> <coding_scheme_code> <reason> <commentary>

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

benchmark_rates delete-many __none__ __none__ system.new_record generated_script

Reads the row's recorded history, newest first.

The command is shaped like this:

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

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

benchmark_rates versions __none__ __none__ --limit 1

Reads one recorded version of the row.

The command is shaped like this:

benchmark_rates version <code> <coding_scheme_code> --version <n>

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

benchmark_rates version __none__ __none__ --version 1