propelorm/Propel — Issue #252: "diff" algorithm
Author: pmarking
Created: 2012-01-06 13:47:16+00:00
State: open

It currently seems that if I run 'propel-gen diff' twice in a row without migrating in between, I will get duplicate migration information, the second of which will usually fail. Wouldn't it make sense for the 'diff' command to do the following:

1. Check the database for the last committed migration (LCM) class/file.
2. Check the directory against that LCM for any uncommitted migration classes/files. If any are found, the diff should fail with a message to the effect that 'Uncommitted migrations have been found; please either commit or delete them before rerunning 'diff'.

Wouldn't that make more sense, or am I misunderstanding the use of the diff and migrate commands?