PostgreSQL:
user A (non-super-user admin account with createdb and createuser)

destiny database:
# main destiny database
user X (job account with read/write)
user Y (api account with read-only)

alliance table:
# Manually created reference info for "meta-clan" groupings
id (int) *primary key*
name (text)
members (jsonb) array of uint32 Bungie clan groupIds

group table:
# Destiny clan info built from alliance.members array of groupId values for each alliance in alliance table
id (bigint) *primary* key which is a Bungie clan groupId
alliance_id (int) *references* alliances entry
updated (timestamp)
detail (jsonb) GroupV2.GetGroup.Response.detail object
founder (jsonb) GroupV2.GetGroup.Response.founder object
members (jsonb) GroupV2.GetMembersOfGroup.Response.results object

account table:
# Destiny account info built from group.members array of objects for each group in group table
membershiptype (int) *composite primary key1* Destiny membershipType from group.members.[index].destinyUserInfo.membershipType value
membershipid (bigint) *composite primary key2* Destiny membershipId from group.members.[index].destinyUserInfo.membershipId value
group_id (bigint) *references* groups entry
alliance_id (int) *references* alliances entry
displayname (text) Destiny displayName from group.members.[index].destinyUserInfo.displayName value
iconpath (text) Destiny iconPath from group.members.[index].destinyUserInfo.iconPath value
updated (timestamp)
accountstats (jsonb) Destiny2.GetHistoricalStatsForAccount.Response object
characterdata (jsonb) Destiny2.GetProfile.Response.characters.data object
characterstats (jsonb) Destiny2.GetHistoricalStats.Response object (meta object built from multiple requests)

# follow @dad2cl3 concept of manifest handling?
manifest_version table:
manifest table:
manifest_stage table:
# Remember to ask why the stage table is needed