Get a clear idea on how to structure and supply database schema migrations #31

New Issue

2020-06-16T15:49:10Z

phryk commented

2020-06-16 15:49:10 +00:00

(Migrated from rnd.phryk.net)

Originally from github issue:

This is probably going to be a bit tricky, since we'll have to automagically generate the needed ALTER TABLE queries for (up to) every custom Storable of the project using poobrains.

This is probably going to be even worse for sqlite which doesn't have extensive support for structural changes of existing tables. Generate a new database at a different spot, migrate content, switcharoo?

Is "chainability" of migrations something that's given?

Also see about whether sqlite -> postgres and vice-versa is possible.

Originally from github issue: > This is probably going to be a bit tricky, since we'll have to automagically generate the needed ALTER TABLE queries for (up to) every custom `Storable` of the project using poobrains. > > This is probably going to be even worse for sqlite which doesn't have extensive support for structural changes of existing tables. Generate a new database at a different spot, migrate content, switcharoo? > > Is "chainability" of migrations something that's given? Also see about whether sqlite -> postgres and vice-versa is possible.

Sign in to join this conversation.