Nuwana - Software Development

Topics 01.Database Migration - Introduction 02.Database Migration - Flyway Vs Liquibase 

  Database Migration GitHub Link For Sample Project: https://github.com/LahiruPriyankara/Liquibase https://github.com/LahiruPriyankara/flyway Git වැනි version control system වලදී code changes history එකක maintain වන අතර එම නිසා කවුද ඒ ඒ changes කලේ කොයිකාලේද කලේ වගේ full history එකක් බලාගන්න පුලුවන් . ඒ වගේම database එකටත් කරන වෙනස්කම් track කරලා තියාගන්න ඕනේ වෙනවනම් එකට use වන version control system තිබෙන අතර flyway, liquibase යනු එවැනි version control system දෙකක් වේ . Database schema changes track කරගන තියන open source version control application එකකි .Any changes which we do with data base scheme will be track and save in flywayschamahistory table in flyway and databasechangelog table in liquibase.   Liquibase or flyway  is an open-source database-independent library for tracking, managing and applying database schema changes.   Advantage Database independent Automatic update (When application up, Changes will be automatically applied.) Au...

Flyway Vs Liquibase GitHub Link For Sample Project: https://github.com/LahiruPriyankara/Liquibase https://github.com/LahiruPriyankara/flyway Differences between Liquibase and Flyway. Flyway  - Use SQL for defining changes. Liquibase  - Use SQL, XML, JSON, YMAL for defining changes (With Liquibase we can work with database-agnostic languages and easily apply schema changes to different database types).  ---------------------------------------------------------------------------------------------------------------------------- Flyway  - Follow file name conventions (a migration should have a convention of prefixes as V (for versioned), U (for undo), and R (for repeatable). It will be followed by a version number and a separator __(two underscores) followed by a description and a suffix .sql such as V01__Add_New_Column.sql). Liquibase  - changes are managed by one ledger known as a master changelog  (db.changelog-master) which will be ...