Timeline for For Evolutionary Database Tools like Flyway or LiquidBase, it is better to integrate the tool or left it as a stand alone step in the CI process?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 21, 2019 at 0:00 | history | tweeted | twitter.com/StackSoftEng/status/1208175474591096837 | ||
| Dec 20, 2019 at 17:00 | comment | added | Thomas Junk | Additionally: Suggested read martinfowler.com/articles/evodb.html | |
| Dec 18, 2019 at 19:04 | answer | added | JimmyJames | timeline score: 3 | |
| Dec 18, 2019 at 16:19 | history | edited | Poutrathor | CC BY-SA 4.0 |
check a limit condition
|
| Dec 18, 2019 at 15:48 | answer | added | Doc Brown | timeline score: 3 | |
| Dec 18, 2019 at 11:13 | comment | added | traneHead | One less, but not one not matching your db. So then you roll back and fix the migration issue | |
| Dec 18, 2019 at 11:10 | comment | added | Poutrathor | If the application does not start you have one less server running. | |
| Dec 18, 2019 at 11:07 | comment | added | traneHead | Concerning option 1 con: The application startup should fail if the database migration fails. (this works with spring/hibernate/liquibase), so if that mechanism is in place you could strike this con. | |
| Dec 17, 2019 at 18:40 | history | asked | Poutrathor | CC BY-SA 4.0 |