Rails 2.3.8 sqlite3 1.3.3 If we run any migration (rake db:migrate) that includes a "remove_index" statement then the index still stays in the sqlite3 datebase.
No errors or exceptions are recieved during the execution. Examples: remove_index :enrollments, :name => :index_team_participations_on_event_id remove_index :enrollments, :name => :index_team_participations_on_country_id remove_index :enrollments, :name => :index_team_participations_on_boat_id remove_index :enrollments, :name => :index_team_participations_on_boat_id_and_event_id Table names and index names were correct in our experiment. You might say that this is not a problem. IT IS. Because when you generate the next migration using "script/generate hobo_migration" , it will regenerate all the remove_index statements. We ended up with an increasing number of remove_indexes during our devepment as we renamed our classes. We posted this as a rails bug. But could anybody offer a workaround. -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.
