Sprig does not check the Schema Version when loading data

[tilo]

there is a risk to load fixtures which are for the incorrect DB schema version -- resulting in incorrectly loaded tables/data.

See also: Sprig is not using a transaction when loading the data

[ltk]

Thanks @tilo! We'll get started looking into both these issues this week and keep you posted.

• Lawson

[ltk]

@tilo could you provide a sample of how you could envision a fix working. How would you tie a particular schema version to the set of seed data? Via top-level configuration? Seed file config?

All the solutions I'm coming up with seem like they would create a lot of busywork updating config every time you created a new migration.