alembic

问题 I am developing a small registration application for a friend zumba class, using Flask, SQLAlchemy and Flask-migrate(alembic) to deal with db update. I settled on SQlite because the application has to be self contained and runs locally on a laptop without internet access and SQLite requires no installation of a service or other, which is a must too. Dealing with SQLite lack of support of ALTER table wasn't a problem during the initial development as I simply destroyed, recreated the DB when

问题 I created a migration with alembic revision --autogenerate , applied it to my development database with alembic upgrade head , and then realised it wasn't quite what I wanted. How can I revert the migration so that I can tweak it and try again? 回答1: Assuming that you only want to go back one revision, use alembic downgrade with a relative migration identifier of -1: alembic downgrade -1 This will run the downgrade() method of your latest revision and update the revision table to indicate the

问题 I created a migration with alembic revision --autogenerate , applied it to my development database with alembic upgrade head , and then realised it wasn't quite what I wanted. How can I revert the migration so that I can tweak it and try again? 回答1: Assuming that you only want to go back one revision, use alembic downgrade with a relative migration identifier of -1: alembic downgrade -1 This will run the downgrade() method of your latest revision and update the revision table to indicate the

来源： https://stackoverflow.com/questions/63746113/add-a-second-db-to-alembic-context

来源： https://stackoverflow.com/questions/63746113/add-a-second-db-to-alembic-context

来源： https://stackoverflow.com/questions/63746113/add-a-second-db-to-alembic-context

问题 I'm not sure how to define a create schema foo migration? My Model looks like this (I'm using Flask-Migrate): class MyTable(db.Model): __tablename__ = "my_table" __table_args__ = {"schema": "foo"} id = ColumnPrimKey() name = Column(Text, unique=True, nullable=False) When I execute mange db upgrade I get a failure because the schema "foo" does not exist. How can I add a migration for the schema with SQLAlchemy and Alembic? 回答1: I accomplished this by modifying the migration upgrade command to

问题 I'm not sure how to define a create schema foo migration? My Model looks like this (I'm using Flask-Migrate): class MyTable(db.Model): __tablename__ = "my_table" __table_args__ = {"schema": "foo"} id = ColumnPrimKey() name = Column(Text, unique=True, nullable=False) When I execute mange db upgrade I get a failure because the schema "foo" does not exist. How can I add a migration for the schema with SQLAlchemy and Alembic? 回答1: I accomplished this by modifying the migration upgrade command to

问题 When deploying an application to a fresh server (i.e. the database is empty) how do I sync the database properly with Flask-Migrate? I've added Flask-Migrate to the project when I already had some schema in place so I don't have "initial" migrations with all create_table() . Now when I do manage.py db upgrade in my deployment script I get relation "..." does not exist . Is there any built-in way to detect empty database and run 'create_all()' instead of migrations? This is what the Alembic's

问题 I'm using SQLAlchemy + alembic to manage my database. I had a string field which was 10 characters long and later on found out that it has to be 20. So I updated the model definition. class Foo(db.Model): __tablename__ = 'foos' id = db.Column(db.Integer, primary_key=True) foo_id = db.Column(db.Integer, db.ForeignKey('users.id')) name = db.Column(db.String(80)) When I run alembic revision --autogenerate , this was not detected. Now I did read the documentation and suspected that this might not