Create New DB Tables #46

New issue

Open

opened 2020-04-08 04:12:28 +02:00 by osilkin98 · 0 comments

osilkin98 commented

2020-04-08 04:12:28 +02:00

(Migrated from github.com)

Database needs a new table to accommodate:

Pinning comments #29
- one-to-many relation PINS: CLAIM -> COMMENT
Channel Blocking
- one-to-many relation BLOCKS: CHANNEL -> CHANNEL
Storing information about claims, including public keys, addresses, stake amounts, etc.
- CLAIM
  - type
  - stake_amount
  - address
  - claim_id
  - name
  - signing_channel
CHANNEL
- public_key
- signature
- public_key_id
Requires making a table CLAIM which stores claim_type, signing_channel, stake_amount
Action history (e.g. channel x edits comment y at time z)
- either loose relation on table CHANNEL or a many-to-many relation between CHANNEL & COMMENT
  - action (creates, deletes, updates, hides, pins, etc.)
  - timestamp (good for modification time, etc.)
  - signature (of the action)
  - comment_id (if there is one)
Messages
- dunno if this will either be a modified signed version of COMMENT or if this should be its own entity entirely

Database needs a new table to accommodate: - Pinning comments #29 - one-to-many relation `PINS`: `CLAIM` -> `COMMENT` - Channel Blocking - one-to-many relation `BLOCKS`: `CHANNEL` -> `CHANNEL` - Storing information about claims, including public keys, addresses, stake amounts, etc. - `CLAIM` - type - stake_amount - address - claim_id - name - signing_channel - `CHANNEL` - public_key - signature - public_key_id - Requires making a table `CLAIM` which stores `claim_type`, `signing_channel`, `stake_amount` - Action history (e.g. channel `x` edits comment `y` at time `z`) - either loose relation on table `CHANNEL` or a many-to-many relation between `CHANNEL` & `COMMENT` - action (creates, deletes, updates, hides, pins, etc.) - timestamp (good for modification time, etc.) - signature (of the action) - comment_id (if there is one) - Messages - dunno if this will either be a modified signed version of `COMMENT` or if this should be its own entity entirely

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/comment-server#46

No description provided.