Something else to consider for 1.1, currently, when using Polymorphic associations, the code doesn't properly build the primary key. Currently, you can work around this by providing :foreign_key.
http://dev.rubyonrails.org/ticket/3820 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dr.Ernie Prabhakar Sent: Monday, February 27, 2006 9:43 AM To: rails-core@lists.rubyonrails.org Subject: Re: [Rails-core] Rails 1.1 is coming Hi Benjamin, On Feb 27, 2006, at 5:59 AM, Benjamin Curtis wrote: > I'm probably one of two people using Rails who really cares about > the little annoyances that come with choosing to use primary key > field names of tablename_id. :) I don't know if it's 1.1 worthy, > but I would like some feedback on http://dev.rubyonrails.org/ticket/ > 3373 -- specifically, what would the preferred location be for a > globally-accessible way to get the primary key field name based on > ActiveRecord::Base.primary_key_prefix_type. This comes up not only > when generating fixtures (the subject of that patch), but also with > schema dump and migrations. > > I have other patches that I use for schema dumping and migrations > that improve the support for > ActiveRecord::Base.primary_key_prefix_type, so it wouldn't take me > long to add some tests and submit a patch if I had a pointer on > where that case statement would best reside. I guess I'm the other one. :-) I run into SQLite databases that use that convention, so I'd use this fix if it were available... -- Ernie P. _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
