This project is archived and is in readonly mode.
remove_index fails SILENTLY on sqlite3
Reported by umur.ozkul (at gmail) | February 1st, 2011 @ 06:17 PM
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.
Comments and changes to this ticket
-
rails May 2nd, 2011 @ 01:00 AM
- State changed from “new” to “open”
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.
Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
-
rails May 2nd, 2011 @ 01:00 AM
- State changed from “open” to “stale”
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
umur.ozkul (at gmail)