When creating an extension model the generator assigns the migration number based on the next number of the application's migration sequence. Normally there is no sequence so the number is 001. The next model generated for the same extension, however, will also get the same sequence number of 001. Things are further complicated when attempting to create a model within the radiant root as the migration number will be based on the last number of the radiant migrations.
The destroy generator also has a problem. When attempting to destroy even the first extension model you get a message claiming that there is no migrations matching that name. This is because the generator is looking in #{RAILS_ROOT}/db/migrate instead of the extension's migration directory.
