Just interested if any Rails developers who use foreign_key_migrations have come up against this or not? I've just raised this potential issue as a bug on RubyForge http://rubyforge.org/tracker/index.php?func=detail&aid=21823&group_id=1699&atid=6632
......
I am discovering when I have the redhill forign_key_migrations & core in place, that when I use rails rake tasks for testing that the database field types created in some cases are incorrect, e.g. creating BIGINT as opposed to INT columns, which causes issues when it tries to setup the foreign keys. Note that when:
(a) create the test database vi " rake db:migrate RAILS_ENV='test' " => This is OK and there are no issues (b) when "rake spec" say uses things such as db:test:purge, db:test:clone, db:schema:load ==> BAD COLUMNS are created. (c) when I delete redhillplugines (core & foreign_key_migrations) & recreate database, I can "rake spec" without an issue
More details below: Macintosh:myequity greg$ rails -v Rails 2.1.0 Macintosh:myequity greg$ ruby -v ruby 1.8.6 (2007-09-23 patchlevel 110) [i686-darwin9.3.0] Macintosh:myequity greg$ gem -v 1.2.0 Macintosh:myequity greg$
================ CASE WHERE ALL IS GOOD ================
Macintosh:myequity greg$ rake db:drop RAILS_ENV="test"