How do I run the engine_settings_fixings commands from the shell?
Table of Contents
This file documents the engine_settings_fixings resource at the shell, one section per command. Every command is a subcommand of engine_settings_fixings, 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:
engine_settings_fixings list [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at reporting.v1.engine_settings_fixings.list.
engine_settings_fixings 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:
engine_settings_fixings get <id>
It is addressed at reporting.v1.engine_settings_fixings.get.
engine_settings_fixings get 00000000-0000-0000-0000-000000000000
1.3. get-many
Reads several rows in one request, one key group per row.
The command is shaped like this:
engine_settings_fixings get-many <id>
It is addressed at reporting.v1.engine_settings_fixings.get_many.
engine_settings_fixings get-many 00000000-0000-0000-0000-000000000000
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:
engine_settings_fixings add <engine_settings_id> <imply_todays_fixings> <include_todays_cash_flows> <include_reference_date_events> <enrich_index_fixings> <ignore_fixing_lag> <ignore_fixing_lead> <reason> <commentary>
It is addressed at reporting.v1.engine_settings_fixings.put.
engine_settings_fixings add 00000000-0000-0000-0000-000000000000 - - - - - - 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:
engine_settings_fixings set <id> <engine_settings_id> <imply_todays_fixings> <include_todays_cash_flows> <include_reference_date_events> <enrich_index_fixings> <ignore_fixing_lag> <ignore_fixing_lead> <reason> <commentary> [--version <n>]
It is addressed at reporting.v1.engine_settings_fixings.put.
engine_settings_fixings set 00000000-0000-0000-0000-000000000000 00000000-0000-0000-0000-000000000000 - - - - - - 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:
engine_settings_fixings put-many --count <n> <id> <engine_settings_id> <imply_todays_fixings> <include_todays_cash_flows> <include_reference_date_events> <enrich_index_fixings> <ignore_fixing_lag> <ignore_fixing_lead> <reason> <commentary>
It is addressed at reporting.v1.engine_settings_fixings.put_many.
engine_settings_fixings put-many --count 1 00000000-0000-0000-0000-000000000000 00000000-0000-0000-0000-000000000000 - - - - - - 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:
engine_settings_fixings delete <id> <reason> <commentary> [--version <n>]
It is addressed at reporting.v1.engine_settings_fixings.delete.
engine_settings_fixings delete 00000000-0000-0000-0000-000000000000 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:
engine_settings_fixings delete-many <id> <reason> <commentary>
It is addressed at reporting.v1.engine_settings_fixings.delete_many.
engine_settings_fixings delete-many 00000000-0000-0000-0000-000000000000 system.new_record generated_script
1.9. by-engine-settings-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:
engine_settings_fixings by-engine-settings-id <engine_settings_id> [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at reporting.v1.engine_settings_fixings.list_by_engine_settings_id.
engine_settings_fixings by-engine-settings-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:
engine_settings_fixings versions <id> [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at reporting.v1.engine_settings_fixings_versions.list.
engine_settings_fixings versions 00000000-0000-0000-0000-000000000000 --limit 1
1.11. version
Reads one recorded version of the row.
The command is shaped like this:
engine_settings_fixings version <id> --version <n>
It is addressed at reporting.v1.engine_settings_fixings_versions.get.
engine_settings_fixings version 00000000-0000-0000-0000-000000000000 --version 1