diff options
| author | Bryan Newbold <bnewbold@robocracy.org> | 2018-03-21 18:46:23 -0700 |
|---|---|---|
| committer | Bryan Newbold <bnewbold@robocracy.org> | 2018-03-21 18:46:23 -0700 |
| commit | d66fed95534d7a443e2cf84e9290d0c9bdf72311 (patch) | |
| tree | 8e4144cd5ff6b4668661468871c8049697d6a05b /plan.txt | |
| parent | e425bdfc377a64613a1cb9995b40be7008440ca2 (diff) | |
| download | fatcat-d66fed95534d7a443e2cf84e9290d0c9bdf72311.tar.gz fatcat-d66fed95534d7a443e2cf84e9290d0c9bdf72311.zip | |
WIP
Diffstat (limited to 'plan.txt')
| -rw-r--r-- | plan.txt | 14 |
1 files changed, 14 insertions, 0 deletions
@@ -1,6 +1,9 @@ +- backend test setup: generate temporary database, insert rows (?) + backend/api: - first-rev schema +- json_blob table (by sha1) - create work, release, etc - get by ID @@ -22,3 +25,14 @@ webface: files people containers + +#### Open Questions + +How to create multiple cross-referenced entities at the same time? Eg, work and +release, with release referencing work. work_id isn't allocated/indicated until +merge-time. As a work-around, could have a temporary work_rev_id column which +gets overridden during merge. + +Mechanism for skipping edit group stage. Propose always having edit rows +generated, containing appropriate metadata, but certain bots can skip creation +of edit group. |