sqlalchemy-bot

Results 828 comments of sqlalchemy-bot

Cookbook recipe for automatic schema migrations for trivial changes

**Michael Bayer ([@zzzeek](https://github.com/zzzeek)) wrote:** right....it would be nice to have. i dont have resources to work on this in the near term, will have to see once i get sqlalchemy...

Cookbook recipe for automatic schema migrations for trivial changes

**Changes by Michael Bayer ([@zzzeek](https://github.com/zzzeek)):** * set **milestone** to "tier 1"

op.add_column() and op.drop_column() should check for SchemaType, run through the events for that type, or perhaps just create/drop

**Wichert Akkerman ([@wichert](https://github.com/wichert)) wrote:** In case it is useful I added a local workaround which adds the type if it is missing: ``` context = alembic.get_context() if context.bind.dialect.name == 'postgresql':...

op.add_column() and op.drop_column() should check for SchemaType, run through the events for that type, or perhaps just create/drop

**Michael Bayer ([@zzzeek](https://github.com/zzzeek)) wrote:** The creation/dropping of the associated type for ENUM and on some platforms boolean is a "schema event" which responds to metadata or Table oncreate/drop. There's currently...

op.add_column() and op.drop_column() should check for SchemaType, run through the events for that type, or perhaps just create/drop

**Michael Bayer ([@zzzeek](https://github.com/zzzeek)) wrote:** correction: bind = alembic.get_bind() typ = ArticleVariant.__table__.c.size_type.type impl = typ.dialect_impl(bind.dialect) impl.create(bind, checkfirst=True) or this: bind = alembic.get_bind() typ = ArticleVariant.__table__.c.size_type.type typ._on_table_create(ArticleVariant.__table__, bind)

op.add_column() and op.drop_column() should check for SchemaType, run through the events for that type, or perhaps just create/drop

**sc68cal ([@sc68cal](https://github.com/sc68cal)) wrote:** Just want to close the loop - I used a similar bit of code that @wichert posted for a [migration in OpenStack Neutron](https://review.openstack.org/#/c/52983/) - just don't forget...

op.add_column() and op.drop_column() should check for SchemaType, run through the events for that type, or perhaps just create/drop

**Anonymous wrote:** Slightly different for me I had to do ``` bind = op.get_bind() typ = ArticleVariant.__table__.c.size_type.type typ._on_table_create(ArticleVariant.__table__, bind, checkfirst=True) ```

op.add_column() and op.drop_column() should check for SchemaType, run through the events for that type, or perhaps just create/drop

**Michael Bayer ([@zzzeek](https://github.com/zzzeek)) wrote:** Issue #280 was marked as a duplicate of this issue.

op.add_column() and op.drop_column() should check for SchemaType, run through the events for that type, or perhaps just create/drop

**Maik Derstappen ([@mrtango](https://github.com/mrtango)) wrote:** I have created a helper file which use the reflection.Inspector and the get_columns method. This also works for checking befor dropping a column. http://www.derstappen-it.de/tech-blog/sqlalchemie-alembic-check-if-table-has-column But it...

op.add_column() and op.drop_column() should check for SchemaType, run through the events for that type, or perhaps just create/drop

**Changes by Michael Bayer ([@zzzeek](https://github.com/zzzeek)):** * changed **title** from "Adding column with native enum fails" to "op.add_column() and op.drop_column() should check "