refactor: consistent pipeline table names and schemas

[nathanielc]

No description provided.

[dav1do]

Looks good, a couple of small questions.

[stbrody]

not sure about this name for this table.

First, is the table actually going to include the proofs? Or just the timestamp conclusions from the proofs? The actual proofs are in the raw_events table right? And then wouldn't this table be derived from raw_events? Or do you actually plan on splitting the raw data for time events to be in a different table than init and data events?

Also I kind of prefer time_proofs to chain_proofs, but that's a minor preference.

[nathanielc]

The intent of this table is to store the ChainInclusionProof structs. This way the conclusion_events table can be built by joining the raw_events table with this table to make time based conclusions. Should we call it chain_inclusion_proofs? It is not the proof contained within the raw events but rather the timestamp and root cid that we know are included in a chain.

[stbrody]

yeah that struct is kind of named weird cause it's not actually storing the proof. It's storing the derived conclusions that come from validating the proof.

How about... time_conclusions?

[nathanielc]

Works for me.

[stbrody]

a few small comments but otherwise LGTM

[stbrody]

Is this "Event Types" table only meant to apply to conclusion events? It's not nested under the conclusion events section of this document. This document also describes the raw events table as well, and in that table init events do have their own event