How do I run the todays_market_configuration_bindings commands from the shell?
Table of Contents
This file documents the todays_market_configuration_bindings resource at the shell, one section per command. Every command is a subcommand of todays_market_configuration_bindings, and every section exports its own script into projects/ores.shell/scripts/library/. Loading a script runs that one command, so a failure names the command it came from.
1. Commands
1.1. list
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:
todays_market_configuration_bindings list [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at analytics.v1.todays_market_configuration_bindings.list.
todays_market_configuration_bindings list --limit 1
1.2. get
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:
todays_market_configuration_bindings get <reference>
It is addressed at analytics.v1.todays_market_configuration_bindings.get.
todays_market_configuration_bindings get __none__
1.3. get-many
Reads several rows in one request, one key group per row.
The command is shaped like this:
todays_market_configuration_bindings get-many <reference>
It is addressed at analytics.v1.todays_market_configuration_bindings.get_many.
todays_market_configuration_bindings get-many __none__
1.4. add
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:
todays_market_configuration_bindings add <todays_market_configuration_id> <collection> <reference> <position> <reason> <commentary>
It is addressed at analytics.v1.todays_market_configuration_bindings.put.
todays_market_configuration_bindings add 00000000-0000-0000-0000-000000000000 __none__ __none__ 0 system.new_record generated_script
1.5. set
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:
todays_market_configuration_bindings set <id> <todays_market_configuration_id> <collection> <reference> <position> <reason> <commentary> [--version <n>]
It is addressed at analytics.v1.todays_market_configuration_bindings.put.
todays_market_configuration_bindings set 00000000-0000-0000-0000-000000000000 00000000-0000-0000-0000-000000000000 __none__ __none__ 0 system.new_record generated_script
1.6. put-many
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:
todays_market_configuration_bindings put-many --count <n> <id> <todays_market_configuration_id> <collection> <reference> <position> <reason> <commentary>
It is addressed at analytics.v1.todays_market_configuration_bindings.put_many.
todays_market_configuration_bindings put-many --count 1 00000000-0000-0000-0000-000000000000 00000000-0000-0000-0000-000000000000 __none__ __none__ 0 system.new_record generated_script
1.7. delete
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:
todays_market_configuration_bindings delete <reference> <reason> <commentary> [--version <n>]
It is addressed at analytics.v1.todays_market_configuration_bindings.delete.
todays_market_configuration_bindings delete __none__ system.new_record generated_script
1.8. delete-many
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:
todays_market_configuration_bindings delete-many <reference> <reason> <commentary>
It is addressed at analytics.v1.todays_market_configuration_bindings.delete_many.
todays_market_configuration_bindings delete-many __none__ system.new_record generated_script
1.9. by-todays-market-configuration-id
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:
todays_market_configuration_bindings by-todays-market-configuration-id <todays_market_configuration_id> [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at analytics.v1.todays_market_configuration_bindings.list_by_todays_market_configuration_id.
todays_market_configuration_bindings by-todays-market-configuration-id 00000000-0000-0000-0000-000000000000 --limit 1
1.10. versions
Reads the row's recorded history, newest first.
The command is shaped like this:
todays_market_configuration_bindings versions <reference> [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at analytics.v1.todays_market_configuration_bindings_versions.list.
todays_market_configuration_bindings versions __none__ --limit 1
1.11. version
Reads one recorded version of the row.
The command is shaped like this:
todays_market_configuration_bindings version <reference> --version <n>
It is addressed at analytics.v1.todays_market_configuration_bindings_versions.get.
todays_market_configuration_bindings version __none__ --version 1