feat(seeding): persistence first-boot seeders and database run-once seeders#73
Merged
Conversation
RegisterPersistenceSeeder (class or delegate form) records seeders that run once, in registration order, after snapshot load and journal replay, only when the save is brand new (no snapshot, no journal). Seed writes go through the normal stores so later boots never re-seed; a seeder failure aborts startup.
RegisterDatabaseSeeder (class or delegate form) records seeders executed by DatabaseService at start, once ever per unique name: applied names are tracked in the __squidstd_seed_history table (synced independently from AutoMigrate), the history row is written only after a successful run so failed seeders retry, and duplicate names fail startup before any seeding.
…remaining seeders
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
IPersistenceSeeder,RegisterPersistenceSeeder<T>()/ delegate form): run once, in registration order, on a FRESH save only (no snapshot, no journal -LastSequenceId == 0after replay), between replay and the autosave loop. Seed writes go through the normal stores, so later boots never re-seed. Fail-fast on seeder exceptions; documented edges: no-op seeders re-run, an emptied-then-snapshotted save re-seeds, mid-sequence failure skips the tail (prefer a single seeder).IDatabaseSeederwithName,RegisterDatabaseSeeder<T>()/(name, delegate)): run once EVER per name, tracked in__squidstd_seed_history(synced independently ofAutoMigrate); the history row is written only after success, so failed seeders retry at the next process start; duplicate names (ordinal) fail startup before any seeding.IReadOnlyList<TSeeder>materialization), interleave plugin-registered seeders naturally, and keep the services container-agnostic via optional ctor parameters.Test plan