title: Good Practices MVC
body: <p>Assume I had a database with two tables:</p>
  
  <p>customer</p>
  
  <p>payment_info</p>
  
  <p>The table customer had fields: name, address, payment_info_id</p>
  
  <p>payment_info_id is a foreign key that links to a row in payment_info. payment_info has fields: id (which is linked to payment_info_id), bank, account number.</p>
  
  <p>Because of my application's logic, each time a customer is created their payment information is stored in a separate row in the payment_info field which is linked to their row in the customer table.</p>
  
  <p>I am using an MVC architecture.</p>
  
  <p>Does it make more sense to keep this 'pure' and make two separate models, one for each table, and then crossload them and call methods from payment_info_controller in customer_controller, or to make a hybrid one which as soon as it creates a row in customer also creates one in payment_info?</p>
  
  <p>Hope this makes sense!</p>