More changes to event sourced table
This commit is contained in:
@@ -6,7 +6,10 @@ description: Runbook for converting an existing SQL table to be event-sourced. T
|
||||
1. The user needs to specify an existing SQL column or other value that exists within the codebase. If this value is unclear, prompt the user
|
||||
2. Before performing any changes, do a thorough investigation for all the call-sites where this value is used in the code
|
||||
# Steps
|
||||
1. Your final goal will be to create a set of three independent changes, stacked on top of each other. Each change below should be its own pull request and create a TODO list for the following steps:
|
||||
* Your final goal will be to create a set of stacked Graphite PRs for each item in this list
|
||||
1. Create a TODO list to track the creation of these PRs
|
||||
2. Steps 4-6 contain changes that are breaking API changes and will need to be merged separately. Create PRs for those anyways but leave them in draft status so that the user can merge them safely
|
||||
|
||||
1. Create a new feature flag to flip between the new data flows
|
||||
2. Create a new SQL ORM entity. At minimum, the entity should contain the following fields:
|
||||
1. A new `PylonId<"Name">`
|
||||
|
||||
Reference in New Issue
Block a user