We should *raise* MissingCurrentMigration :)

Thanks for the catch, Elrond.
This commit is contained in:
Christopher Allan Webber 2011-07-13 20:58:13 -05:00
parent c2ddd85e4a
commit 511b10efda

View File

@ -173,7 +173,7 @@ class MigrationManager(object):
with the 'current_migration', throw an error.
"""
if self.database_current_migration() is None:
MissingCurrentMigration(
raise MissingCurrentMigration(
"Tried to call function which requires "
"'current_migration' set in database")