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

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

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

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

curve_sections get <code>

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

curve_sections get __none__

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

The command is shaped like this:

curve_sections get-many <code>

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

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

curve_sections add <code> <entry_element> <description> <reason> <commentary>

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

curve_sections add __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:

curve_sections set <code> <entry_element> <description> <reason> <commentary> [--version <n>]

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

curve_sections set __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:

curve_sections put-many --count <n> <code> <entry_element> <description> <reason> <commentary>

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

curve_sections put-many --count 1 __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:

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

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

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

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

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

curve_sections delete-many __none__ system.new_record generated_script

Reads the row's recorded history, newest first.

The command is shaped like this:

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

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

curve_sections versions __none__ --limit 1

Reads one recorded version of the row.

The command is shaped like this:

curve_sections version <code> --version <n>

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

curve_sections version __none__ --version 1