A relevant question that i think is appropriate for this thread: can
anybody please explain to me the purpose of primary_key type in context
of migrations:
t.primary_key :person_id
?
The migration
class CreateInstructors < ActiveRecord::Migration
def self.up
create_table :instructors do |t|
t.primary_key :person_id
t.text :presentation
...
does not work (SQLite3::SQLException: table "instructors" has more than
one primary key: ... during migration),
but
class CreateInstructors < ActiveRecord::Migration
def self.up
create_table :instructors, :primary_key => "person_id" do |t|
t.primary_key :person_id
t.text :presentation
...
and
class CreateInstructors < ActiveRecord::Migration
def self.up
create_table :instructors, :primary_key => "person_id" do |t|
t.text :presentation
...
seem to have completely identical effect:-/.
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" 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/rubyonrails-talk?hl=en.
