Hy. I don't now if this is the correct post for do this question, but I have a problem like this. Until today I used alembic in a project and had worked perfectly, the db contain tables created previously than aren't in the models object of my project, but whenever I do a migration with autogenerate, alembic donìt detect them. But today I do a migration and in the upgrade Alembic try to dropped every table not reflected in my models. I don't understand why
Il giorno venerdì 3 febbraio 2012 18:50:54 UTC+1, André Dieb ha scritto: > > Hello, > > I'm trying to start using alembic for future migrations, replacing > sqlalchemy-migrate. > > My database is already very populated and I tried to follow the > Tutorial steps, starting by initing it, then configuring env.py to > autogenerate revisions. > > My problem is: when I run revision --autogenerate, it detects all my > tables as deleted and in the end detects some changes correctly. How > do I tell alembic my tables already exist? > > Thanks in advance -- 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.
