Page History

...

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.

Status

Discussion thread. Further discussion.

Status

Accepted. Vote thread. Vote resultUnder discussion.

Who is Involved

• Unknown User (adamsaghy) (original proposal, PMC member)Victor Manual Romero Rodriguez (risk assessment, PMC memberrisk 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, PMC memberreviewer)
• 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

...

Alternatives Considered

None.

Phases of work

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