Using alembic downgrade, it's impossible to cancel the initial revision

[vporton]

Describe the bug
Using alembic downgrade, it's impossible to cancel the initial revision:

Running alembic downgrade 2ba30ccd01a7, does not drop the tables added by the initial migration 2ba30ccd01a7 (despite downgrade() script is correct).

Expected behavior
Need a way to downgrade to the state before the initial migration (for example, to run the initial migration again after this).

Error
No error message.

Versions.

• OS: Ubuntu
• Python: 3.9.16
• Alembic: 1.12.0
• SQLAlchemy: 2.0.22
• Database: Posgres
• DBAPI: psycopg2

[CaselIT]

Hi,

use base instead. the downgrade command reads as downgrade to the provided revision.
Admittedly the docs could be clearer, like the command line help does not mention base or head.

@zzzeek anything against improving upon the docs / command line help?

[zzzeek]

Sure, though this is documented? literally the section called downgrading illustrates downgrading to base.

@vporton were the docs not clear here?

[CaselIT]

yes, but doing alembic upgrade -h or alembic downgrade -h makes no mention if it

[zzzeek]

"base" is just one of many kinds of identifiers that can be passed, which might not be appropriate in a multi-base environment. there's also relative revision identifiers, etc.