error: cannot drop sequence drizzle.__drizzle_migrations_id_seq because other objects depend on it

[JohnCido]

[✓] Pulling schema from database...

 Warning  You are about to execute current statements:

DROP SEQUENCE "drizzle"."__drizzle_migrations_id_seq";

error: cannot drop sequence drizzle.__drizzle_migrations_id_seq because other objects depend on it
    at .../node_modules/drizzle-kit/bin.cjs:79476:15
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Object.query (.../node_modules/drizzle-kit/bin.cjs:121418:26)
    at async pgPush (.../node_modules/drizzle-kit/bin.cjs:124361:13)
    at async _Command.<anonymous> (.../node_modules/drizzle-kit/bin.cjs:131618:7) {
  length: 343,
  severity: 'ERROR',
  code: '2BP01',
  detail: 'default value for column id of table drizzle.__drizzle_migrations depends on sequence drizzle.__drizzle_migrations_id_seq',
  hint: 'Use DROP ... CASCADE to drop the dependent objects too.',
  position: undefined,
  internalPosition: undefined,
  internalQuery: undefined,
  where: undefined,
  schema: undefined,
  table: undefined,
  column: undefined,
  dataType: undefined,
  constraint: undefined,
  file: 'dependency.c',
  line: '1202',
  routine: 'reportDependentObjects'
}

[JohnCido]

Using latest drizzle-kit

[abhishek-butola]

Having same issue. It works on initial db:push. After making a change repush gives this error

works fine on 0.22.7

[rainspelldev]

Same here.

I'm using a Supabase database and whenever I run drizzle-kit push it tries to drop the following sequences and then fails with a similar error message:

DROP SEQUENCE "auth"."refresh_tokens_id_seq";
DROP SEQUENCE "pgsodium"."key_key_id_seq";
DROP SEQUENCE "graphql"."seq_schema_version";
DROP SEQUENCE "drizzle"."__drizzle_migrations_id_seq";
DROP SEQUENCE "realtime"."subscription_id_seq";
DROP SEQUENCE "realtime"."messages_id_seq";

error: cannot drop sequence auth.refresh_tokens_id_seq because other objects depend on it

This did not happen with version 0.22.7.

[MrOxMasTer]

I use postgresql. The same mistake.

First there was an error with ssl, which I fixed in the configuration:

dbCredentials: {
    ...
    ssl: false,
  },

Then this error occurred
drizzle-kit v0.23.0
I used drizzle-up - it doesn't help

[MrOxMasTer]

I just deleted the id_seq and I managed to make a push 😂
Thank you for this pet Project. But after such moments, I realized that drizzle is not yet ready to be used in production practice

[kimdanielarthur-cowlabs]

Also get the same error as OP

[AirZona]

same issue, works fine with v0.22.8

and get the error: default value for column id of table drizzle.__drizzle_migrations depends on sequence drizzle.__drizzle_migrations_id_seq with version 0.23.0

Thanks!

[martinamps]

+1

[jonmarada]

Encountering the same issue with PostgreSQL on Neon had to go back to version v0.22.8, seems to work fine from there.

[krunalmiracle]

Same error "DROP SEQUENCE \"pgsodium\".\"key_key_id_seq\";"
On postgresql log in supabase, gives the following error

Event message
must be owner of sequence key_key_id_seq
Severity
ERROR

Timestamp
2024-07-22T13:29:11.332Z

Postgres Username
postgres

Session ID
669e5ea4.93da

Metadata
{
  "file": null,
  "host": "db-host hidden text",
  "metadata": [],
  "parsed": [
    {
      "application_name": "postgres.js",
      "backend_type": "client backend",
      "command_tag": "DROP SEQUENCE",
      "connection_from": "Hidden-ipv6",
      "context": null,
      "database_name": "postgres",
      "detail": null,
      "error_severity": "ERROR",
      "hint": null,
      "internal_query": null,
      "internal_query_pos": null,
      "leader_pid": null,
      "location": null,
      "process_id": 37850,
      "query": "DROP SEQUENCE \"pgsodium\".\"key_key_id_seq\";",
      "query_id": query id hidden,
      "query_pos": null,
      "session_id": "hidden session id",
      "session_line_num": 4,
      "session_start_time": "2024-07-22 13:29:08 UTC",
      "sql_state_code": "42501",
      "timestamp": "2024-07-22 13:29:11.332 UTC",
      "transaction_id": 0,
      "user_name": "postgres",
      "virtual_transaction_id": "8/4726"
    }
  ],
  "parsed_from": null,
  "project": null,
  "source_type": null

Though already modified the drizzle config to ignore the supabase internal schemas.

	dialect: 'postgresql',
	schema: './src/lib/server/schemas/schemas.ts',
	out: './drizzle',
	dbCredentials: {
		url: connectionString
	},
	// Added this line to exclude pgsodium and other Supabase-managed schemas and only use "public" schema
	schemaFilter: ["public"],
	// Explicitly exclude Supabase's internal schemas
	tablesFilter: ['!pgsodium.*', '!auth.*', '!storage.*', '!graphql.*', '!graphql_public.*', '!realtime.*', '!supabase_functions.*'],
});

[T04435]

Not a solution for PROD envs, but...

I had this error while setting up the project and I'm on yolo push mode.

DO NOT USE IN PROD

• connect to your DB
• open drizzle schema > delete entries from migrations table
• delete local migrations (including meta folder)
• run drizzle-kit generate then migrate

"drizzle-kit": "^0.23.0",

Still looking for a proper solution...

[AndriiSherman]

Hey, sorry everyone, I just noticed this issue. I'm working on fixing it now. It seems like drizzle-kit is not filtering some sequences that should not be used in the push process. I'll try to make this fix as soon as possible.

By the way, on July 30th, drizzle-kit will be open-sourced, so I hope you can find solutions for such problems faster

[Naeem-gg]

Hey, sorry everyone, I just noticed this issue. I'm working on fixing it now. It seems like drizzle-kit is not filtering some sequences that should not be used in the push process. I'll try to make this fix as soon as possible.

By the way, on July 30th, drizzle-kit will be open-sourced, so I hope you can find solutions for such problems faster

Thank you @AndriiSherman

[AndriiSherman]

Please try the drizzle-kit@seq_fix version. If that fixes your problem, I'll include it in the latest release asap

I would also suggest using the verbose and strict flags to ensure the push is doing what's expected

[skycoop]

That test version seems to resolve the issue for me. Ran push before and after installing the version and could confirm that the error went away. Looking forward to it being released 😁