An unexpected error occurred. Please try again.

[steve-taylor]

I tried running this command in the console and received the error shown below it:

I did this after trying to drizzle-kit push:mysql, which resulted in the following output:

npm run db:push

> [email protected] db:push
> drizzle-kit push:mysql --schema src/db/schema.ts --driver mysql2 --connectionString $(npm run -s db:connection)

drizzle-kit: v0.19.8
drizzle-orm: v0.27.2

/Users/me/GITHUB/my-org/my-app/node_modules/drizzle-kit/index.cjs:35334
        const localErr = new Error();
                         ^

Error: unknown: uncaught panic: interface conversion: interface is nil, not sqlparser.Expr, vtgate: http://pscluster-miyqinj80g7y-aws-apsoutheast2b-1-vtgate-aee5a9e5qph6c:15000/
    at PromiseConnection.execute (/Users/me/GITHUB/my-org/my-app/node_modules/drizzle-kit/index.cjs:35334:26)
    at fromDatabase (/Users/me/GITHUB/my-org/my-app/node_modules/drizzle-kit/index.cjs:11824:33)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async mysqlPushIntrospect (/Users/me/GITHUB/my-org/my-app/node_modules/drizzle-kit/index.cjs:37623:19)
    at async Command.<anonymous> (/Users/me/GITHUB/my-org/my-app/node_modules/drizzle-kit/index.cjs:52731:31) {
  code: 'ER_UNKNOWN_ERROR',
  errno: 1105,
  sql: 'SELECT table_name, column_name\n' +
    '  FROM information_schema.table_constraints t\n' +
    '  LEFT JOIN information_schema.key_column_usage k\n' +
    '  USING(constraint_name,table_schema,table_name)\n' +
    "  WHERE t.constraint_type='PRIMARY KEY'\n" +
    "      and table_name != '__drizzle_migrations'\n" +
    '      AND t.table_schema = ?',
  sqlState: 'HY000',
  sqlMessage: 'unknown: uncaught panic: interface conversion: interface is nil, not sqlparser.Expr, vtgate: http://pscluster-miyqinj80g7y-aws-apsoutheast2b-1-vtgate-aee5a9e5qph6c:15000/'
}

This worked yesterday, but no longer works today. Was there a recent change pushed to PlanetScale that broke something, or is there currently a partial outage?

Update: PlanetScale seems to be choking on the USING keyword. I rewrote the query using ON instead and it worked:

SELECT t.table_name, k.column_name
  FROM information_schema.table_constraints t
  LEFT JOIN information_schema.key_column_usage k
  ON t.constraint_name = k.constraint_name
  AND t.table_schema = k.table_schema
  AND t.table_name = k.table_name
  WHERE t.constraint_type = 'PRIMARY KEY'
      AND t.table_name != '__drizzle_migrations'
      AND t.table_schema = 'myschema';

but this doesn't explain why drizzle-kit push:mysql worked yesterday and not today.

[steve-taylor]

drizzle-kit 0.19.6 changed the query to use USING which seems to be unsupported by PlanetScale.

[steve-taylor]

Reopening, because Planetscale does in fact support USING, but it seems to be busted on my instance.