I don't get: "❗ MySQL schemas/database are no longer supported by drizzle-kit Drizzle Kit won't handle any schema changes for additional schemas/databases in your drizzle schema file"

[newsve]

Does it mean I cannot do any change of my mysql db anymore or just migrations, but still be able to push (so the declarative way)? Or I can do still both work but not for a second db. Would be great if anyone could elaborate

[tushargoyalofficial]

I guess they are dropping support for MySQL database.

[newsve]

Yeah, but the message isn't fully consistent: In the title they say it's no longer supported, then in the body text they add "for additional", so I would assume one schema, database is allowed.

Whatever the message isn't clear and would be great if the team could clarify the message a bit.

[AlexBlokh]

hey @newsve @tushargoyalofficial

Unlike PostgreSQL, MySQL schemas are not the same. MySQL so called schemas are databases and thus we've made a wrong decision to try to support them with Drizzle Kit from the beginning

For proper understanding I'll plot the hierarchy of particular dialects:

• PostgreSQL: server -> database -> schema -> tables
• MySQL: server -> database(so called schema) -> tables
• SQLite: file / database -> tables

We can't treat MySQL database as schema, we now treat it as a devops property, just like PostgreSQL database property on Postgres Server. We now treat MySQL database/schema as SQLite attachable database.

We fully support querying cross MySQL databases with Drizzle ORM.
We fully support all schema changes migrations for MySQL with Drizzle Kit.
We don't generate create database, drop database, etc. migrations with Drizzle Kit, since those are not in the domain of schema, those are in the domain of devops. Thus when you declare MySQL tables within schemas with Drizzle ORM - Drizzle Kit ignores them, because unlike PostgreSQL - there's no public schema in MySQL.

I hope that makes sense now

[stagr]

We fully support querying cross MySQL databases with Drizzle ORM.

@AlexBlokh, I suppose this means that we need to change our implementation (that have two MySQL schemas) into two different drizzle schemas which each are used to create a separate drizzle instance (connection)? Do you mean that Drizzle can handle querying across tables in these two instances?

Do you have any examples or guidelines for cross MySQL database queries?

[tushargoyalofficial]

Hey @AlexBlokh
Thanks for the information. So, Can we interpret it like drizzle-kit generate/migrate commands going to stop working for MySQL. Sorry I am bit confused over here. Can you suggest some good alternatives to it ?

[AlexBlokh]

It works and it covers 100% of usecases, that should be covered for schema changes

[newsve]

Apologies, for asking again, I am even more confused by you last reply. So, can I still drizzle-kit push ts schema changes to MySQL, e.g. PlanetScale, or not?

[AlexBlokh]

I updated my answer, it's hard to explain because of the misleading terminology of SQL databases. There're schema for tables structure, schema as a folder of tables in Postgres which is both DATABASE and SCHEMA in MySQL

Doing my best to avoid confusion

[exchai93]

I am trying to push a mysql schema to a new database in my planet scale organisation.. is this why I am coming across errors when I try to run drizzle commands db:push and db:studio?

If this is the case what is the alternative to make updates from the mysql 'schema' database definition in schema.ts?

Dependencies:
"mysql2": "^3.11.0"
"drizzle-orm": "^0.31.2"
"drizzle-kit": "^0.22.7"
"@planetscale/database": "^1.18.0"