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

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

It is addressed at reporting.v1.ore_file_versions.list.

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

ore_file_versions get <id>

It is addressed at reporting.v1.ore_file_versions.get.

ore_file_versions get 00000000-0000-0000-0000-000000000000

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

The command is shaped like this:

ore_file_versions get-many <id>

It is addressed at reporting.v1.ore_file_versions.get_many.

ore_file_versions get-many 00000000-0000-0000-0000-000000000000

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:

ore_file_versions add <ore_file_code> <engine_version> <content> <sha256> <bytes> <reason> <commentary>

It is addressed at reporting.v1.ore_file_versions.put.

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

ore_file_versions set <id> <ore_file_code> <engine_version> <content> <sha256> <bytes> <reason> <commentary> [--version <n>]

It is addressed at reporting.v1.ore_file_versions.put.

ore_file_versions set 00000000-0000-0000-0000-000000000000 __none__ __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:

ore_file_versions put-many --count <n> <id> <ore_file_code> <engine_version> <content> <sha256> <bytes> <reason> <commentary>

It is addressed at reporting.v1.ore_file_versions.put_many.

ore_file_versions put-many --count 1 00000000-0000-0000-0000-000000000000 __none__ __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:

ore_file_versions delete <id> <reason> <commentary> [--version <n>]

It is addressed at reporting.v1.ore_file_versions.delete.

ore_file_versions delete 00000000-0000-0000-0000-000000000000 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:

ore_file_versions delete-many <id> <reason> <commentary>

It is addressed at reporting.v1.ore_file_versions.delete_many.

ore_file_versions delete-many 00000000-0000-0000-0000-000000000000 system.new_record generated_script

Reads one page of the rows that share a relation value. The relation is part of the address rather than a filter applied after the read.

The command is shaped like this:

ore_file_versions by-ore-file-code <ore_file_code> [--offset <n>] [--limit <n>] [--order <field>] [--desc]

It is addressed at reporting.v1.ore_file_versions.list_by_ore_file_code.

ore_file_versions by-ore-file-code __none__ --limit 1

Reads the row's recorded history, newest first.

The command is shaped like this:

ore_file_versions versions <id> [--offset <n>] [--limit <n>] [--order <field>] [--desc]

It is addressed at reporting.v1.ore_file_versions_versions.list.

ore_file_versions versions 00000000-0000-0000-0000-000000000000 --limit 1

Reads one recorded version of the row.

The command is shaped like this:

ore_file_versions version <id> --version <n>

It is addressed at reporting.v1.ore_file_versions_versions.get.

ore_file_versions version 00000000-0000-0000-0000-000000000000 --version 1