How do I run the equity_underlyings commands from the shell?
Table of Contents
This file documents the equity_underlyings resource at the shell, one section per command. Every command is a subcommand of equity_underlyings, 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:
equity_underlyings list [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at refdata.v1.equity_underlyings.list.
equity_underlyings 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:
equity_underlyings get <code>
It is addressed at refdata.v1.equity_underlyings.get.
equity_underlyings get __none__
1.3. get-many
Reads several rows in one request, one key group per row.
The command is shaped like this:
equity_underlyings get-many <code>
It is addressed at refdata.v1.equity_underlyings.get_many.
equity_underlyings 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:
equity_underlyings add <code> <name> <description> <instrument_type> <resolves_to> <currency_code> <display_order> <reason> <commentary>
It is addressed at refdata.v1.equity_underlyings.put.
equity_underlyings add __none__ __none__ __none__ __none__ __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:
equity_underlyings set <code> <name> <description> <instrument_type> <resolves_to> <currency_code> <display_order> <reason> <commentary> [--version <n>]
It is addressed at refdata.v1.equity_underlyings.put.
equity_underlyings set __none__ __none__ __none__ __none__ __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:
equity_underlyings put-many --count <n> <code> <name> <description> <instrument_type> <resolves_to> <currency_code> <display_order> <reason> <commentary>
It is addressed at refdata.v1.equity_underlyings.put_many.
equity_underlyings put-many --count 1 __none__ __none__ __none__ __none__ __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:
equity_underlyings delete <code> <reason> <commentary> [--version <n>]
It is addressed at refdata.v1.equity_underlyings.delete.
equity_underlyings 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:
equity_underlyings delete-many <code> <reason> <commentary>
It is addressed at refdata.v1.equity_underlyings.delete_many.
equity_underlyings delete-many __none__ system.new_record generated_script
1.9. versions
Reads the row's recorded history, newest first.
The command is shaped like this:
equity_underlyings versions <code> [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at refdata.v1.equity_underlyings_versions.list.
equity_underlyings versions __none__ --limit 1
1.10. version
Reads one recorded version of the row.
The command is shaped like this:
equity_underlyings version <code> --version <n>
It is addressed at refdata.v1.equity_underlyings_versions.get.
equity_underlyings version __none__ --version 1