I understand why that approach makes sense, but this does feel like a bug for those of us who use this type of naming convention. For example, with the current SchemaDumper, here's some sample output:
Oh definitely, the current behaviour is a bug, I just don't think the right solution is to change the behaviour of create_table to transparently use that setting. Instead it's in two parts: 1) allow create table to take an :id=>:something_id argument 2) Make the schema dumpers recognise the alternate primary keys, and dump that new format. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
