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

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

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

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

calendar_names get <code>

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

calendar_names get __none__

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

The command is shaped like this:

calendar_names get-many <code>

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

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

calendar_names add <code> <description> <reason> <commentary>

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

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

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

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

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

calendar_names put-many --count <n> <code> <description> <reason> <commentary>

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

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

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

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

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

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

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

calendar_names delete-many __none__ system.new_record generated_script

Reads the row's recorded history, newest first.

The command is shaped like this:

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

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

calendar_names versions __none__ --limit 1

Reads one recorded version of the row.

The command is shaped like this:

calendar_names version <code> --version <n>

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

calendar_names version __none__ --version 1