[Koha-bugs] [Bug 27880] Store each database migrations state in database

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27880

--- Comment #33 from David Cook <dcook at prosentient.com.au> ---
When in doubt, I like to look at existing implementations and resources.

Ruby on Rails is known for its migrations:
https://guides.rubyonrails.org/v3.2/migrations.html#what-s-in-a-name

"For example Alice adds migrations 20080906120000 and 20080906123000 and Bob
adds 20080906124500 and runs it. Alice finishes her changes and checks in her
migrations and Bob pulls down the latest changes. When Bob runs rake
db:migrate, Rails knows that it has not run Alice’s two migrations so it
executes the up method for each migration.

Of course this is no substitution for communication within the team. For
example, if Alice’s migration removed a table that Bob’s migration assumed to
exist, then trouble would certainly strike."

This is similar to what I was saying at
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27880#c26

I don't know enough about the RM/RMaint process, but it sounds like they'll
need to be very careful with backporting any migrations so that they don't
allow conflicting migrations / migrations will need to be written carefully. 

But I don't think that's a reason not to proceed.

-- 
You are receiving this mail because:
You are watching all bug changes.