Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat(db): support MySQL/MariaDB and Aurora as production databases

Open
  • Is something wrong?
#49 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, java, mariadb, mysql, postgresql
Domain
build-system, ci-cd, database, documentation, infrastructure

Research direction

Start by reading the datasource configuration and the Flyway adoption work in #22, then check how Quarkus selects JDBC drivers and how the native build registers them. The issue calls for MySQL/MariaDB and Aurora support, portable or vendor-specific migrations, a PostgreSQL and MySQL CI matrix, and database connection documentation; done means those pieces work together.

Written by the indexing model from the issue text.

Description

enhancement help wanted java
Problem Statement

Production is effectively limited to PostgreSQL. DATASOURCE_DB_KIND accepts h2 or postgresql (%prod defaults to postgresql; H2 is dev-only). Operators standardized on MySQL/MariaDB or AWS Aurora cannot run ThrillhouseBot on their existing managed database. This is not a hard design constraint — Panache/Hibernate and Quarkus support multiple JDBC dialects.

Proposed Solution
  • Add the JDBC driver extensions (e.g. quarkus-jdbc-mysql, quarkus-jdbc-mariadb) and accept additional DATASOURCE_DB_KIND values. Aurora MySQL/PostgreSQL are wire-compatible with the respective drivers.
  • Ensure schema migrations are portable across dialects (coordinate with the Flyway adoption in #22 — either dialect-neutral SQL or per-vendor migration paths).
  • Register the new drivers for the GraalVM native build and add a CI test matrix (at least PostgreSQL + MySQL).
  • Document supported databases and connection settings.
Alternatives Considered
  • Stay PostgreSQL-only and document it — simplest, but excludes MySQL/Aurora shops.
Priority

Important

Code of Conduct
  • I have searched for existing issues and this is not a duplicate.
Dominant language
Java
Stars
35
Forks
7
Avg merge
9h 23m
Merged PRs (30d)
154

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from devops-thiago/ThrillhouseBot

All issues in devops-thiago/ThrillhouseBot

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.