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

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

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

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

calendars get <code>

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

calendars get __none__

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

The command is shaped like this:

calendars get-many <code>

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

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

calendars add <code> <name> <calendar_type> <country_code> <image_id> <source> <is_editable> <base_calendar_code> <reason> <commentary>

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

calendars add __none__ __none__ __none__ __none__ __none__ __none__ false __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:

calendars set <code> <name> <calendar_type> <country_code> <image_id> <source> <is_editable> <base_calendar_code> <reason> <commentary> [--version <n>]

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

calendars set __none__ __none__ __none__ __none__ __none__ __none__ false __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:

calendars put-many --count <n> <code> <name> <calendar_type> <country_code> <image_id> <source> <is_editable> <base_calendar_code> <reason> <commentary>

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

calendars put-many --count 1 __none__ __none__ __none__ __none__ __none__ __none__ false __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:

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

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

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

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

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

calendars delete-many __none__ system.new_record generated_script

Reads the row's recorded history, newest first.

The command is shaped like this:

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

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

calendars versions __none__ --limit 1

Reads one recorded version of the row.

The command is shaped like this:

calendars version <code> --version <n>

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

calendars version __none__ --version 1