Upgrades with postgres SQL scripts fail due to rename of engine to postgresql

qizhiyi / sqlalchemy-migrate

Automatically exported from code.google.com/p/sqlalchemy-migrate

MIT License

0 stars 0 forks source link

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

For details see

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592876

SQLAlchemy 0.6.3
sqlalchemy-migrate 0.6

Original issue reported on code.google.com by jan.ditt...@gmail.com on 13 Aug 2010 at 7:07

GoogleCodeExporter commented 8 years ago

Can you or the OP provide steps to reproduce this?

Original comment by cwith...@gmail.com on 14 Jan 2011 at 7:23

GoogleCodeExporter commented 8 years ago

I asked the OP to provide the required information.

Original comment by jan.ditt...@gmail.com on 14 Jan 2011 at 7:43

GoogleCodeExporter commented 8 years ago

Original comment by jan.ditt...@gmail.com on 14 Feb 2011 at 6:48

GoogleCodeExporter commented 8 years ago

I think this is the same problem as issue 83

Original comment by wyue...@gmail.com on 2 Oct 2011 at 11:43

GoogleCodeExporter commented 8 years ago

the issue is fixed for new changesets (issue 83) existing repositories will not 
be migrated to use "postgresql" though.

Original comment by jan.ditt...@gmail.com on 28 Oct 2011 at 9:40