model level booleans coming through autogen should at least be complete

[sqlalchemy-bot]

Migrated issue, originally created by Anonymous

When I make new revision with --autogenerate options for new boolean column I get this migration script

#!python
def upgrade():
    ### commands auto generated by Alembic - please adjust! ###
...
    sa.Column('is_grand', sa.Boolean(), nullable=True),
    sa.CheckConstraint('TODO'),
...

The script is running with error:

sqlalchemy.exc.ProgrammingError: (ProgrammingError) column "todo" does not exist

What does it mean TODO?
Does alembic support sqlachemy boolean type?

[sqlalchemy-bot]

Michael Bayer (@zzzeek) wrote:

it means that autogenerate does not render the SQL text of a CheckConstraint just yet. A Boolean may have a CheckConstraint associated with it, if the backend only supports integers. I'm not sure why in your case it is actually spitting the constraint out, though, it should be implicit with the Boolean type, since some backends shouldn't be getting the constraint.

[sqlalchemy-bot]

Changes by Michael Bayer (@zzzeek):

• changed title from "Does alembic sqlachemy boolean type support?" to "model level booleans coming through autogen should"

[sqlalchemy-bot]

Anonymous wrote:

Yes, I thought so about.

Thanks for the quick reply.

[sqlalchemy-bot]

Michael Bayer (@zzzeek) wrote:

this is fixed regarding unnecessary gen of the CheckConstraint associated with Boolean, and also the SQL text of CheckConstraint is rendered for those constraints that are actually present explicitly. [[https://bitbucket.org/zzzeek/alembic/changeset/f579cfeda37763bfe93268a20b534f2f79b4a0dc|f579cfeda37763bfe93268a20b534f2f79b4a0dc]]

[sqlalchemy-bot]

Changes by Michael Bayer (@zzzeek):

• changed status to closed