ores.iam.account_party

Table of Contents

Junction table linking IAM accounts to parties. Each account can be associated with one or more parties, controlling which parties a user can act on behalf of.

1. Flags

2. Left

ID of the IAM account.

References ores_iam_accounts_tbl.id (soft FK).

ctx.generate_uuid()

3. Right

ID of the party this account is associated with.

References ores_refdata_parties_tbl.id (soft FK).

ctx.generate_uuid()

4. Columns

5. SQL

5.1. Flags

6. Foreign keys

6.1. account_id

ID of the IAM account; must exist in ores_iam_accounts_tbl.

6.2. party_id

ID of the party this account is associated with; must exist in ores_refdata_parties_tbl.

7. Repository

8. C++

8.1. Flags

8.2. Domain includes

#include <chrono>
#include <string>
#include <boost/uuid/uuid.hpp>

8.3. Entity includes

#include <string>
#include "sqlgen/Timestamp.hpp"
#include "sqlgen/PrimaryKey.hpp"

8.4. Conventions

8.5. Table display

column header
account_id Account
party_id Party
modified_by Modified By
version Version

8.6. Presentation

The screen's declaration. An association has no key field to name: the model declares none, because an association is identified by the pair it links and a single field cannot state half of a pair. The view addresses it by the pair, one path segment each, and the key record the descriptor states carries both. That is why :key_field: is absent here and present on every entity that has one.

8.6.1. Detail fields

field label widget type is_key is_required placeholder
account_id Account accountEdit line_edit true true  
party_id Party partyEdit line_edit true true  

8.6.2. Columns

enum_name field header type width
AccountId account_id Account string 320
PartyId party_id Party string 320

9. See also

  • ores.iam — component group overview.

Emacs 29.3 (Org mode 9.6.15)