How are people organising migrations

Usage Stories
1

Hi all

pls forgive me if this is the wrong place for question like this, if so, just let me know and I’ll head on over to the correct place.

I’m curious how people are organising migrations. Mostly around how they ensure migrations “don’t break” because they’ve already been ran. For example, are people doing something railsesq and storing a list of already ran migration effectively ensuring a given migration only runs once? Or writing some sort of guard to look for the intended effect then running if ‘ok’? Or just swallowing errors and moving on? Or…?

2

ROM for rom-sql use Sequel for migration. So everything you can read here is valid:
http://sequel.jeremyevans.net/rdoc/files/doc/migration_rdoc.html
http://sequel.jeremyevans.net/rdoc/files/doc/schema_modification_rdoc.html

you can choose how migrations will be numerated and sequel will create special table inside db to keep track of all already applied

2 Likes