joelniemela / maggy Goto Github PK

Change config.ini to connect to the database Maggy using the user Maggy and no password with the host set to localhost.

Currently, maggy help doesn't give much information at all. A short description and a longer description should be added for each command, as well as a quick description of Maggy syntax, accessible with the maggy help syntax command.

All lose top-level functions should be organized into classes, and those classes should be organized into files (preferably one file per class).

Currently, if the maggy rollback command is run, but the correct migration file isn't found, Maggy throws the confusing error "Nothing to migrate; already at version {current version}."

The attributes --#Breaking and --#IgnoreData should be implemented with the following behaviors:

--#Breaking:

• Force a migration to go through even if it fails the test.
• Gives a warning when trying to rollback the migration.

--#IgnoreData:

• Force a migration to go through, even if it might cause data loss or corruption.
• Gives a notice when trying to rollback the migration.