Axel Fontaine - Database migrations with Flyway #3

Activity

1. arun-gupta

   changed the title [-]Axel Fontaine[/-] [+]Axel Fontaine - Database migrations with Flyway[/+] on Jan 16, 2015
2. arun-gupta commented on Jan 16, 2015

   

   arun-gupta

   on Jan 16, 2015

   ContributorAuthor

   More actions

   • How do developers do db migrations without flyway
   • Getting started samples
   • How does it interact with JPA
   • Comparison with Liquibase
   • IDE support
3. javornikolov commented on Jan 17, 2015

   

   javornikolov

   on Jan 17, 2015

   More actions

   • With changes of a db object scattered in multiple migration files: it might get hard to collect the bigger picture (the whole current state of the object and of the schema as a whole). How do we keep clarity on the big picture?
   • Reverting database schema changes
   • At install time is selected which modules to install. Later may install the skipped ones. (Module=subset of migrations). So depending on the environment - order of applying migrations (in same schema) might be different. Any hints for such scenarios?
4. devopsd commented on Jan 20, 2015

   

   devopsd

   on Jan 20, 2015

   More actions

   How do you add index on big table on DB running in production without blocking deployment pipeline?
5. devopsd commented on Jan 20, 2015

   

   devopsd

   on Jan 20, 2015

   More actions

   Does Flyway support migration rollbacks?
6. cesarhernandezgt commented on Jan 20, 2015

   

   cesarhernandezgt

   on Jan 20, 2015

   More actions

   Common case scenarios of Flyway for testing environment.
7. arun-gupta commented on Feb 13, 2015

   

   arun-gupta

   on Feb 13, 2015

   ContributorAuthor

   More actions

   Hanginar link: https://plus.google.com/events/cq4df8h3pvvfipt1htppldj8qj0

   Feb 18, Wednesday, 9:30am PT.
8. giates commented on Feb 19, 2015

   

   giates

   on Feb 19, 2015

   More actions

   Hi,

   this is not an issue but a suggestion based on my experience...

   I'm using Flyway on some of JEE7 projects and under Glassfish 4.1 I've found a little gotcha, see http://stackoverflow.com/questions/27881538/flyway-wrongly-load-and-execute-migration-definitions-of-each-ejb-module-of-de

   In few words, if you've more than one ejb module with flyway migrations avoid to put the SQL migrations under db.migraion folder, instead use a folder with unique name for each different ejb module, then set the folder location during flyway process inizialization...

   Hope this helps...