Brendon Whateley wrote: > Be very careful doing this. When you change assumed Rails conventions > and behavior, it tends to bite you in unexpected ways. While you can > override the ID column, I'd suggest not doing it. > > I'd seriously just let Rails add an extra ID column and put the big > table in other columns. The cost is small and you are not potentially > breaking future Rails stuff.
+1. Mapping legacy IDs onto default Rails IDs will bite. -- Roderick van Domburg http://www.nedforce.com -- 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 -~----------~----~----~----~------~----~------~--~---
