Summary

Only support Postgres. Remove MariaDB and MySQL support.

This is a SIGNIFICANT improvement with huge potential gain and some risks to mitigate.

This proposal is only our agreement on a single database; to proceed and remove code and documentation related specifically to MariaDB and MySQL. With this proposal we will make an effort but we are not committing to migration guides, scripts, tests, tools, wizards, and case studies easing database migrations. The community is strongly encouraged to gather real-world data, to share and discuss this proposal with all users, encouraging them to create or sponsor creation of these critically important migration materials.

Discussion thread

Status

Accepted. Vote thread. Vote result.

Who is Involved

• Unknown User (adamsaghy) (original proposal, risk assessment)
• Nidhi Bhawari (reviewer)
• Unknown User (bgowda) (reviewer)
• Tito Mari Francis Escaño (reviewer)
• Ambika (reviewer)
• Unknown User (awasum) (reviewer, risk assessment)
• Vignesh E (reviewer)
• Paul Christison (reviewer)
• Unknown User (meonkeys) (FSIP author, reviewer)
• Edward Kang (reviewer)
• Victor Manual Romero Rodriguez (reviewer, risk assessment)
• james dailey (reviewer)
• Attila Budai (reviewer)
• Aleksandar Vidakovic (reviewer)
• Aman Mittal (reviewer)
• Mohammed Saifulhuq (reviewer)
• Jose Alberto Hernandez (reviewer)

Background/Motivation

• Speed up development, simplify maintenance
  
  • support one SQL flavor only
  • less edge/corner cases to manage
  • more reliable testing
  • faster CI build
• Leverage Postgres-specific features
  • sequences / identity columns for primary keys
  • native table partitioning
  • safer and more efficient transaction integrity support
  • more advanced indexing options
• Improve security

Goals and Exclusions

• Consolidate all relational database storage logic to work with Postgres only.
• Inform community and provide hints and tips for deployments needing to migrate to Postgres.
• Encourage entire community (especially all users: banks, vendors, and paid support orgs) to write or sponsor MariaDB/MySQL to Postgres migration guides, scripts, tests, tools, wizards, case studies, etc.
• We recognize this is a major improvement not without risk. See comments by Victor and others in the discussion thread about anticipated risk. We commit to mitigating the risk as much as possible while we commit ourselves to making difficult, informed, and courageous choices on how best to maintain Fineract.

Change Proposed

Remove code and documentation related specifically to MariaDB and MySQL.

Best effort migration support only. Volunteers, users, banks, vendors, and paid support orgs are expected to create or sponsor creation of anything useful for deployments needing to migrate.

Alternatives Considered

None.

Phases of work

1. DISCUSS
2. VOTE
3. TRACK
4. CLOSE