-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support MySQL Database Backend #7
Labels
discussion
Requires further discussion before implementing
Comments
Very interested |
Sounds good, can I ask what the situation is that needs or prefers MySQL? Just curious to learn more! |
We're running Vitess (OSS behind Planetscale), that already has backups, management, etc. We wouldn't add Postgres / SQLite to our infra just for a REST catalog |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The database backends are all based on SQL queries "compiled" using SQLC to Go code. So it shouldn't be too difficult to add another support for MySQL on top of Postgres and SQLite. Would anyone be interested in this? I ask because the purpose of the current backends are:
MySQL would be an alternative to Postgres, but is it as popular? Are there popular database services based on MySQL? For example, Planetscale is one (https://planetscale.com/).
The text was updated successfully, but these errors were encountered: