[ 
https://issues.apache.org/jira/browse/FINERACT-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18106491#comment-18106491
 ] 

Sonigra Bhavya Hemendrabhai commented on FINERACT-2704:
-------------------------------------------------------

Hi [~meonkeys],

I’m testing the {{1.15.0}} database rebaseline locally. The core baseline 
({{{}0001{}}}/{{{}0002{}}}) runs successfully, but Liquibase crashes 
immediately afterward on the module scripts (e.g. {{{}fineract-loan{}}}).

*The issue:* The {{pg_dump}} used for {{0001_initial_schema.sql}} captured the 
_entire_ database. Since all module tables are now hardcoded into the Core 
baseline, the old module scripts crash with "relation already exists" when they 
try to run.

How do you want to handle the architecture here?
 # *Monolithic:* Delete all the old migration scripts inside the individual 
module folders so they match the single core dump?
 # *Hybrid:* Replace the current {{0001}} with a "Core-only" dump so the 
existing module scripts can still run cleanly on top, keeping modules fully 
decoupled?
 # *Strict Modular:* Manually split the massive {{pg_dump}} into separate 
baselines for each module?

> re-baseline database migrations
> -------------------------------
>
>                 Key: FINERACT-2704
>                 URL: https://issues.apache.org/jira/browse/FINERACT-2704
>             Project: Apache Fineract
>          Issue Type: Improvement
>          Components: Build
>            Reporter: Adam Monsen
>            Priority: Minor
>              Labels: beginner
>         Attachments: Screenshot 2026-08-20 at 11.18.23 PM.png
>
>
> {{./gradlew devRun}} is pretty slow for a fresh database. Part of the reason 
> is that many liquibase database migrations need to run.
> Re-baseline our db migrations as of the current release (1.15.0): create an 
> empty database, run all migrations, then re-create initial schema and initial 
> data files. Leave any schema/data migrations created post-1.15.0 in place, 
> but you may re-number all initial and migration files starting at 0001.
> We'll plan on doing this once per release, back to the last supported/stable 
> release.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to