This project is archived and is in readonly mode.
Improve schema_dumper handling of :primary_key
Reported by Ryan Carver | August 28th, 2008 @ 11:41 PM | in 2.x
When using the composite_primary_keys plugin, the schema_dumper fails to print the primary key. The refactoring in the attached patch maintains the current behavior while allowing composite_primary_keys to enable dumping a multi-value primary key.
Comments and changes to this ticket
-
josh December 15th, 2008 @ 08:57 PM
- State changed from new to open
-
Pratik December 21st, 2008 @ 04:53 PM
- Assigned user set to Pratik
- State changed from open to invalid
This is generating wrong schema.rb when I tried with sqlite3 :
Before :
create_table "items", :force => true do |t| t.string "name" t.datetime "created_at" t.datetime "updated_at" end
After :
create_table "items", :id => false, :force => true do |t| t.string "name" t.datetime "created_at" t.datetime "updated_at" end
Thanks.
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>