This project is archived and is in readonly mode.
table_name_prefix with db:schema:load causes double prefixes
2: create some migrations. For example:
create_table :blogs do |t| t.string :name t.timestamps end
rake db:migrate. The generated schema is as
create_table "pfx_blogs", :force => true do |t| t.string "name" t.timestamps end create_table "pfx_schema_migrations", :primary_key => "version", :force => true do |t| end add_index "pfx_schema_migrations", ["version"], :name => "unique_schema_migrations", :unique => true
rake test. The tables created by
db:schema:load are as follows:
Additionally, I don't know whether this is related, but under
SQLite3, I get the following on
rake test after a
SQLite3::SQLException: index unique_schema_migrations already exists: CREATE UNIQUE INDEX "unique_schema_migrations" ON "pfx_schema_migrations" ("version")
Comments and changes to this ticket
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.
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>