How do I run the netting_sets commands from the shell?
Table of Contents
This file documents the netting_sets resource at the shell, one section per command. Every command is a subcommand of netting_sets, 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:
netting_sets list [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at refdata.v1.netting_sets.list.
netting_sets 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:
netting_sets get <code>
It is addressed at refdata.v1.netting_sets.get.
netting_sets get __none__
1.3. get-many
Reads several rows in one request, one key group per row.
The command is shaped like this:
netting_sets get-many <code>
It is addressed at refdata.v1.netting_sets.get_many.
netting_sets 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:
netting_sets add <code> <party_id> <netting_agreement_id> <credit_limit_id> <counterparty_id> <call_type> <initial_margin_type> <risk_weight> <description> <reason> <commentary>
It is addressed at refdata.v1.netting_sets.put.
netting_sets add __none__ 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:
netting_sets set <id> <code> <party_id> <netting_agreement_id> <credit_limit_id> <counterparty_id> <call_type> <initial_margin_type> <risk_weight> <description> <reason> <commentary> [--version <n>]
It is addressed at refdata.v1.netting_sets.put.
netting_sets set 00000000-0000-0000-0000-000000000000 __none__ 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:
netting_sets put-many --count <n> <id> <code> <party_id> <netting_agreement_id> <credit_limit_id> <counterparty_id> <call_type> <initial_margin_type> <risk_weight> <description> <reason> <commentary>
It is addressed at refdata.v1.netting_sets.put_many.
netting_sets put-many --count 1 00000000-0000-0000-0000-000000000000 __none__ 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:
netting_sets delete <code> <reason> <commentary> [--version <n>]
It is addressed at refdata.v1.netting_sets.delete.
netting_sets 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:
netting_sets delete-many <code> <reason> <commentary>
It is addressed at refdata.v1.netting_sets.delete_many.
netting_sets delete-many __none__ system.new_record generated_script
1.9. by-netting-agreement-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:
netting_sets by-netting-agreement-id <netting_agreement_id> [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at refdata.v1.netting_sets.list_by_netting_agreement_id.
netting_sets by-netting-agreement-id - --limit 1
1.10. by-credit-limit-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:
netting_sets by-credit-limit-id <credit_limit_id> [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at refdata.v1.netting_sets.list_by_credit_limit_id.
netting_sets by-credit-limit-id - --limit 1
1.11. versions
Reads the row's recorded history, newest first.
The command is shaped like this:
netting_sets versions <code> [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at refdata.v1.netting_sets_versions.list.
netting_sets versions __none__ --limit 1
1.12. version
Reads one recorded version of the row.
The command is shaped like this:
netting_sets version <code> --version <n>
It is addressed at refdata.v1.netting_sets_versions.get.
netting_sets version __none__ --version 1