On Wed, Dec 12, 2018 at 1:01 PM patrick payet wrote:
>
> I had a SQLAlchemy model like -
>
> class User(DeclarativeBase):
> __tablename__ = 'users'
>
> id = Column(BigInteger, primary_key=True)
> email = Column(String(100), unique=True, nullable=False)
> name =
On Wed, Dec 12, 2018 at 10:40 AM wrote:
>
> Dear Alembic User Community,
>
> I am looking for suggestion for the best way to address the following problem:
>
> We have a use case where we'd like to make sure some SQL queries are always
> executed after any set migration.
> Our particular use
I had a SQLAlchemy model like -
class User(DeclarativeBase):
__tablename__ = 'users'
id = Column(BigInteger, primary_key=True)
email = Column(String(100), unique=True, nullable=False)
name = Column(String(100), nullable=False)
hashed_password = Column(String(100),
Dear Alembic User Community,
I am looking for suggestion for the best way to address the following
problem:
We have a use case where we'd like to make sure some SQL queries are always
executed after any set migration.
Our particular use case is with PostgreSQL. We have several users who can