How do I run the ore_files 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_files list [--offset <n>] [--limit <n>] [--order <field>] [--desc]

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

ore_files 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_files get <code>

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

ore_files get __none__

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

The command is shaped like this:

ore_files get-many <code>

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

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

ore_files add <code> <name> <category_code> <configuration_type_code> <guide_section> <origin> <format> <schema_ore_file_code> <typical_filename> <filename_regex> <description> <display_order> <reason> <commentary>

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

ore_files add __none__ __none__ __none__ - - __none__ __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_files set <code> <name> <category_code> <configuration_type_code> <guide_section> <origin> <format> <schema_ore_file_code> <typical_filename> <filename_regex> <description> <display_order> <reason> <commentary> [--version <n>]

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

ore_files set __none__ __none__ __none__ - - __none__ __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_files put-many --count <n> <code> <name> <category_code> <configuration_type_code> <guide_section> <origin> <format> <schema_ore_file_code> <typical_filename> <filename_regex> <description> <display_order> <reason> <commentary>

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

ore_files put-many --count 1 __none__ __none__ __none__ - - __none__ __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_files delete <code> <reason> <commentary> [--version <n>]

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

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

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

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

ore_files delete-many __none__ 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_files by-category-code <category_code> [--offset <n>] [--limit <n>] [--order <field>] [--desc]

It is addressed at reporting.v1.ore_files.list_by_category_code.

ore_files by-category-code __none__ --limit 1

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_files by-configuration-type-code <configuration_type_code> [--offset <n>] [--limit <n>] [--order <field>] [--desc]

It is addressed at reporting.v1.ore_files.list_by_configuration_type_code.

ore_files by-configuration-type-code - --limit 1

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_files by-schema-ore-file-code <schema_ore_file_code> [--offset <n>] [--limit <n>] [--order <field>] [--desc]

It is addressed at reporting.v1.ore_files.list_by_schema_ore_file_code.

ore_files by-schema-ore-file-code - --limit 1

Reads the row's recorded history, newest first.

The command is shaped like this:

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

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

ore_files versions __none__ --limit 1

Reads one recorded version of the row.

The command is shaped like this:

ore_files version <code> --version <n>

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

ore_files version __none__ --version 1