tapaswenipathak commented on code in PR #2648: URL: https://github.com/apache/fineract/pull/2648#discussion_r998230919
########## fineract-doc/src/docs/en/chapters/architecture/persistence.adoc: ########## @@ -62,3 +62,129 @@ The switch from Flyway (1.6.x) to Liquibase (1.7.x) was planned to be as smooth * If the database is empty, Liquibase will create the database schema from scratch * If the database contains the latest Fineract 1.6.x database structure which was previously migrated with Flyway. Liquibase will seamlessly upgrade it to the latest version. Note: the Flyway related 2 database tables are left as they are and are not deleted. * If the database contains an earlier version of the database structure than Fineract 1.6.x. Liquibase will *NOT* do anything and *will fail the application during startup*. The proper approach in this case is to first upgrade your application version to the latest Fineract 1.6.x so that the latest Flyway changes are executed and then upgrade to the newer Fineract version where Liquibase will seamlessly take over the database upgrades. + +== Tuning and Indexing + +To optimize performance based on PostgreSQL and Eclipselink enhancements, tuning Review Comment: cc @mdallos. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
