ptrdom commented on issue #94: URL: https://github.com/apache/pekko-persistence-r2dbc/issues/94#issuecomment-6440136279
Status update and a look at what else might be worth supporting. Currently supported: PostgreSQL, YugabyteDB, MySQL, H2. Oracle is in progress. SQL Server will be ported from Akka once its BSL change date passes (~2027-02). Other candidates, roughly by value: 1. **MariaDB**: has its own R2DBC driver (`org.mariadb:r2dbc-mariadb`) and has drifted from MySQL (JSON, `RETURNING`, some DDL). First step is running the MySQL dialect tests against MariaDB; it may only need a CI job and docs, or a small dialect variant. 2. **CockroachDB**: `design-notes.md` already lists it as a design target, but it isn't tested. Uses the Postgres driver. Expected gaps: SERIALIZABLE-by-default retries, `SERIAL`/`unique_rowid()` ordering semantics, and some function/`ON CONFLICT` differences. Note it's no longer open-source core (CockroachDB Software License), though it's usable in CI. 3. **IBM Db2**: official R2DBC driver exists (`com.ibm.db2:db2-r2dbc`). Mostly enterprise demand, similar audience to Oracle; the CI container is heavy. Probably best left until someone needs it and can help maintain it. Likely not worth a dedicated dialect: - TiDB (MySQL-compatible) and managed Postgres/MySQL offerings (Aurora, AlloyDB, Neon, etc.): should work with existing dialects; a docs note is enough. - Cloud Spanner: has a driver, but no real local container and different transaction semantics. - ClickHouse/analytical stores: not a good fit for an event journal. Suggested order: MariaDB → CockroachDB → Db2 on demand. Separate issues per database as before, so specifics don't pile up here. Contributions welcome. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
