Re: alembic autogenerated migrations do not see current tables
That was it, thanks!
On Wednesday, November 21, 2018 at 6:57:10 PM UTC+1, Mike Bayer wrote:
>
> you need to have include_schemas=True in your env.py:
>
>
> https://alembic.zzzcomputing.com/en/latest/api/runtime.html?highlight=include_schemas#alembic.runtime.environment.EnvironmentContext.configure.params.include_schemas
>
>
>
> On Wed, Nov 21, 2018 at 11:49 AM Riccardo Magliocchetti
> > wrote:
> >
> > Hello,
> >
> > for some reason at each migration alembic does not find any table or
> index and
> > creates them from scratch. Assuming this is not something other people
> are
> > seeing, the only thing peculiar to our setup is that we are using
> postgresql
> > schemas.
> >
> > e.g. I've added a deleted column and the diff between the autogenerated
> > migrations is something like this (edited):
> >
> > --- 103ed8fb3bca_.py2018-11-21 15:28:38.117308742 +0100
> > +++ 96adf3b68cc9_.py2018-11-21 17:08:02.132233306 +0100
> > @@ -1,27 +1,23 @@
> > """empty message
> >
> > -Revision ID: 103ed8fb3bca
> > -Revises:
> > -Create Date: 2018-11-21 09:58:27.765255
> > +Revision ID: 96adf3b68cc9
> > +Revises: 6204f8cedea2
> > +Create Date: 2018-11-21 16:08:02.128288
> >
> > [...]
> >
> > # revision identifiers, used by Alembic.
> > -revision = '103ed8fb3bca'
> > -down_revision = None
> > +revision = '96adf3b68cc9'
> > +down_revision = '6204f8cedea2'
> > @@ -95,6 +90,7 @@
> > sa.Column('xmin', sa.Integer(), server_default=FetchedValue(),
> > nullable=True, system=True),
> > sa.Column('name', sa.UnicodeText(), nullable=False),
> > sa.Column('organization_id', sa.Integer(), nullable=False),
> > +sa.Column('deleted', sa.Boolean(), nullable=True),
> > sa.ForeignKeyConstraint(['organization_id'],
> > ['organization.organization.id'], ),
> > sa.PrimaryKeyConstraint('id'),
> > sa.UniqueConstraint('id', 'organization_id'),
> >
> > Any hint on what could be wrong? We are using alembic 1.0.2.
> >
> > Thanks in advance
> >
> > --
> > Riccardo Magliocchetti
> > @rmistaken
> >
> > http://menodizero.it
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "sqlalchemy-alembic" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to sqlalchemy-alembic+unsubscr...@googlegroups.com .
>
> > For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy-alembic" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sqlalchemy-alembic+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: alembic autogenerated migrations do not see current tables
you need to have include_schemas=True in your env.py:
https://alembic.zzzcomputing.com/en/latest/api/runtime.html?highlight=include_schemas#alembic.runtime.environment.EnvironmentContext.configure.params.include_schemas
On Wed, Nov 21, 2018 at 11:49 AM Riccardo Magliocchetti
wrote:
>
> Hello,
>
> for some reason at each migration alembic does not find any table or index and
> creates them from scratch. Assuming this is not something other people are
> seeing, the only thing peculiar to our setup is that we are using postgresql
> schemas.
>
> e.g. I've added a deleted column and the diff between the autogenerated
> migrations is something like this (edited):
>
> --- 103ed8fb3bca_.py2018-11-21 15:28:38.117308742 +0100
> +++ 96adf3b68cc9_.py2018-11-21 17:08:02.132233306 +0100
> @@ -1,27 +1,23 @@
> """empty message
>
> -Revision ID: 103ed8fb3bca
> -Revises:
> -Create Date: 2018-11-21 09:58:27.765255
> +Revision ID: 96adf3b68cc9
> +Revises: 6204f8cedea2
> +Create Date: 2018-11-21 16:08:02.128288
>
> [...]
>
> # revision identifiers, used by Alembic.
> -revision = '103ed8fb3bca'
> -down_revision = None
> +revision = '96adf3b68cc9'
> +down_revision = '6204f8cedea2'
> @@ -95,6 +90,7 @@
> sa.Column('xmin', sa.Integer(), server_default=FetchedValue(),
> nullable=True, system=True),
> sa.Column('name', sa.UnicodeText(), nullable=False),
> sa.Column('organization_id', sa.Integer(), nullable=False),
> +sa.Column('deleted', sa.Boolean(), nullable=True),
> sa.ForeignKeyConstraint(['organization_id'],
> ['organization.organization.id'], ),
> sa.PrimaryKeyConstraint('id'),
> sa.UniqueConstraint('id', 'organization_id'),
>
> Any hint on what could be wrong? We are using alembic 1.0.2.
>
> Thanks in advance
>
> --
> Riccardo Magliocchetti
> @rmistaken
>
> http://menodizero.it
>
> --
> You received this message because you are subscribed to the Google Groups
> "sqlalchemy-alembic" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sqlalchemy-alembic+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy-alembic" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sqlalchemy-alembic+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
