fix documentation meta.bind(engine) -> meta.bind = engine; thanks mvt
This commit is contained in:
parent
27c3cca5a2
commit
384f045de8
@ -158,11 +158,11 @@ Our change script defines two functions, currently empty:
|
|||||||
)
|
)
|
||||||
|
|
||||||
def upgrade(migrate_engine):
|
def upgrade(migrate_engine):
|
||||||
meta.bind(migrate_engine)
|
meta.bind = migrate_engine
|
||||||
account.create()
|
account.create()
|
||||||
|
|
||||||
def downgrade(migrate_engine):
|
def downgrade(migrate_engine):
|
||||||
meta.bind(migrate_engine)
|
meta.bind = migrate_engine
|
||||||
account.drop()
|
account.drop()
|
||||||
|
|
||||||
As you might have guessed, :func:`upgrade` upgrades the database to the next
|
As you might have guessed, :func:`upgrade` upgrades the database to the next
|
||||||
@ -277,10 +277,10 @@ Your application defines a table in the model.py file:
|
|||||||
import model
|
import model
|
||||||
|
|
||||||
def upgrade(migrate_engine):
|
def upgrade(migrate_engine):
|
||||||
model.meta.bind(migrate_engine)
|
model.meta.bind = migrate_engine
|
||||||
|
|
||||||
def downgrade(migrate_engine):
|
def downgrade(migrate_engine):
|
||||||
model.meta.bind(migrate_engine)
|
model.meta.bind = migrate_engine
|
||||||
model.table.drop()
|
model.table.drop()
|
||||||
|
|
||||||
This runs successfully the first time. But what happens if we change
|
This runs successfully the first time. But what happens if we change
|
||||||
@ -302,10 +302,10 @@ We'll create a new column with a matching change script
|
|||||||
import model
|
import model
|
||||||
|
|
||||||
def upgrade(migrate_engine):
|
def upgrade(migrate_engine):
|
||||||
model.meta.bind(migrate_engine)
|
model.meta.bind = migrate_engine
|
||||||
model.table.data.create()
|
model.table.data.create()
|
||||||
def downgrade(migrate_engine):
|
def downgrade(migrate_engine):
|
||||||
model.meta.bind(migrate_engine)
|
model.meta.bind = migrate_engine
|
||||||
model.table.data.drop()
|
model.table.data.drop()
|
||||||
|
|
||||||
This appears to run fine when upgrading an existing database - but the
|
This appears to run fine when upgrading an existing database - but the
|
||||||
|
@ -18,9 +18,6 @@ del _sa_version
|
|||||||
from migrate.changeset.schema import *
|
from migrate.changeset.schema import *
|
||||||
from migrate.changeset.constraint import *
|
from migrate.changeset.constraint import *
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
sqlalchemy.schema.Table.__bases__ += (ChangesetTable, )
|
sqlalchemy.schema.Table.__bases__ += (ChangesetTable, )
|
||||||
sqlalchemy.schema.Column.__bases__ += (ChangesetColumn, )
|
sqlalchemy.schema.Column.__bases__ += (ChangesetColumn, )
|
||||||
sqlalchemy.schema.Index.__bases__ += (ChangesetIndex, )
|
sqlalchemy.schema.Index.__bases__ += (ChangesetIndex, )
|
||||||
|
Loading…
x
Reference in New Issue
Block a user