fix: seed demo content from the current schema#796
Open
anonymoususer72041 wants to merge 3 commits into
Open
Conversation
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.
Fixes #572
This PR changes the demo installation flow so demo content is no longer restored from a full legacy database backup. Instead, demo installations now load the current base schema from
db/cats_schema.sqlfirst and then apply demo-only seed data fromdb/cats_demo_data.sql.The new demo seed contains only data intended to be applied on top of the current schema. It does not include schema definitions, historical
module_schemastate or base lookup data that already belongs todb/cats_schema.sql. This avoids treating demo content as an old installation that has to pass through legacy upgrade behavior.The installer path for demo data now follows the same current-schema starting point as a fresh installation and then adds the demo records on top. Existing non-demo installation and legacy upgrade paths are left unchanged.
The old
db/cats_testdata.bakdemo database snapshot has been removed because it is no longer used by the active demo installation flow.