Skip to content

docs(readme): clarify Vitess/MySQL vs Postgres #6

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.

Sign up for GitHub

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

Merged
bddicken merged 3 commits into from
May 6, 2026
+2 −0
Merged

docs(readme): clarify Vitess/MySQL vs Postgres #6

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3b2b8a1
docs(readme): clarify Vitess/MySQL vs Postgres
SimeonGriggs May 6, 2026
adfd144
docs(readme): simplify Vitess/MySQL note
SimeonGriggs May 6, 2026
2dbe2e0
docs(readme): use Postgres instead of PostgreSQL in note
SimeonGriggs May 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
# Learn how to integrate PlanetScale with a sample Django application

> **Note:** This tutorial targets PlanetScale Vitess/MySQL. PlanetScale also offers managed Postgres. For more information, see the [PlanetScale Postgres documentation](https://planetscale.com/docs/postgres).

This sample application demonstrates how to connect to a PlanetScale MySQL database, create and run migrations, seed the database, and display the data.

For the full tutorial, see the [Django PlanetScale documentation](https://planetscale.com/docs/tutorials/connect-django-app).
Expand Down
Loading