I am leery of migrating my perfectly stable and fine production data base.
But I need to add some customer info to my system. I am adding a new model backed by a database for the new customer info. Thus I'm assuming that I won't need to migrate the old database. The change is that there is a new database. However the existing production database will need a ':has_one' for the new database. This is the change I need to make to the production database of Orders. The new database will hold download links and passwords, for some orders, So I need the new database (Order_Download) to contain the above fields (download_link and password) plus the foreign key order_id, and the old database (Orders) will contain an ':has_one' to associate it with Order_Download. So I have: class Order < ActiveRecord::Base has_one: order_download // NEW, ADDING TO PRODUCTION DATABASE class OrderDownload < ActiveRecord::Base // new database belongs_to :order The question is, can I just add this and nothing will break, nothing needs migrating, everything is cool? Or am I changing the production database Orders with a new ':has_one' which is going to require me to do something painful? Like migrate, yuck. Sorry I'm a database newbie and I'd rather not mess with it. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
