How do I run the party_countries 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:

party_countries list [--offset <n>] [--limit <n>] [--order <field>] [--desc]

It is addressed at refdata.v1.party_countries.list.

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

party_countries get <party_id> <country_alpha2_code>

It is addressed at refdata.v1.party_countries.get.

party_countries get 00000000-0000-0000-0000-000000000000 __none__

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

The command is shaped like this:

party_countries get-many <party_id> <country_alpha2_code>

It is addressed at refdata.v1.party_countries.get_many.

party_countries get-many 00000000-0000-0000-0000-000000000000 __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:

party_countries add <party_id> <country_alpha2_code> <reason> <commentary>

It is addressed at refdata.v1.party_countries.put.

party_countries add 00000000-0000-0000-0000-000000000000 __none__ 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:

party_countries set <party_id> <country_alpha2_code> <reason> <commentary> [--version <n>]

It is addressed at refdata.v1.party_countries.put.

party_countries set 00000000-0000-0000-0000-000000000000 __none__ 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:

party_countries put-many --count <n> <party_id> <country_alpha2_code> <reason> <commentary>

It is addressed at refdata.v1.party_countries.put_many.

party_countries put-many --count 1 00000000-0000-0000-0000-000000000000 __none__ 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:

party_countries delete <party_id> <country_alpha2_code> <reason> <commentary> [--version <n>]

It is addressed at refdata.v1.party_countries.delete.

party_countries delete 00000000-0000-0000-0000-000000000000 __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:

party_countries delete-many <party_id> <country_alpha2_code> <reason> <commentary>

It is addressed at refdata.v1.party_countries.delete_many.

party_countries delete-many 00000000-0000-0000-0000-000000000000 __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:

party_countries by-party-id <party_id> [--offset <n>] [--limit <n>] [--order <field>] [--desc]

It is addressed at refdata.v1.party_countries.list_by_party_id.

party_countries by-party-id 00000000-0000-0000-0000-000000000000 --limit 1