Menu
Squawk LogoSquawkDocsRules
PlaygroundQuick StartGitHub
Squawk LogoSquawk
  • Docs
  • Rules
  • Playground
  • Quick Start
  • GitHub
  • General
    • Quick Start
    • Applying migrations safely
    • CLI
    • GitHub Integration
    • Web Frameworks
    • Postgres locks and further reading
    • Troubleshooting
  • Rules
    • Rules Overview
    • adding-field-with-default
    • adding-foreign-key-constraint
    • adding-not-nullable-field
    • adding-required-field
    • adding-serial-primary-key-field
    • ban-char-field
    • ban-concurrent-index-creation-in-transaction
    • ban-drop-column
    • ban-drop-database
    • ban-drop-not-null
    • ban-drop-table
    • changing-column-type
    • constraint-missing-not-valid
    • disallowed-unique-constraint
    • prefer-bigint-over-int
    • prefer-bigint-over-smallint
    • prefer-identity
    • prefer-robust-stmts
    • prefer-text-field
    • prefer-timestamptz
    • renaming-column
    • renaming-table
    • require-concurrent-index-creation
    • require-concurrent-index-deletion
    • transaction-nesting
    • ban-create-domain-with-constraint
    • ban-alter-domain-with-add-constraint
    • ban-truncate-cascade

ban-drop-table

problem#

Dropping a table may break existing clients.

solution#

Update your application code to no longer read or write the table.

Once the table is no longer needed, you can delete it by running the command "DROP TABLE mytable;".

This command will permanently remove the table from the database and all its contents.

Be sure to back up the table before deleting it, just in case you need to restore it in the future.

Edit this page
Previous
« ban-drop-not-null
Next
changing-column-type »
  • problem
  • solution

Docs

  • Quick Start
  • Rules

More

  • GitHub
  • Changelog
  • Help
Copyright © 2025 Squawk Authors.