[
https://issues.apache.org/jira/browse/FINERACT-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Monsen updated FINERACT-2704:
----------------------------------
Description:
{{./gradlew devRun}} is pretty slow for a fresh database. Part of the reason is
that many liquibase database migrations need to run.
Confirm that's true, then re-baseline our db migrations as of the current
release (1.15.0 as of the time of writing, but 1.16.0 will be out soon so use
that if so): 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/1.16.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.
was:
{{./gradlew devRun}} is pretty slow for a fresh database. Part of the reason is
that many liquibase database migrations need to run.
Confirm that's true, then 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.
> 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
>
> {{./gradlew devRun}} is pretty slow for a fresh database. Part of the reason
> is that many liquibase database migrations need to run.
> Confirm that's true, then re-baseline our db migrations as of the current
> release (1.15.0 as of the time of writing, but 1.16.0 will be out soon so use
> that if so): 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/1.16.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)
