title: Which approach should i go for regarding relations in Room DB?
body: <p>I'm doing a simple shop-app to learn more about Room DB in Android and currently I'm a bit confused on which approach is the best to go with when it comes to relations and nested objects.</p>
  
  <p><strong>Scenario:</strong> Customer choose an item from the shop and orders it. Afterward the database updates the customer-table with the order ID so the customers orders can be searched in the DB. The order-table have the products ID's in that specific order. In customers "account" page <em>(inside the app)</em>, all the orders including the products should be displayed with all necessary informations (e.g order id, product name, price, quantity etc.).</p>
  
  <p>I've made this sketch to illustrate the three tables: customer, order and product
  <a href="https://i.stack.imgur.com/q4JYC.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/q4JYC.png" alt="enter image description here"></a> </p>
  
  <p><strong>Question:</strong> What is <code>@Foreign key</code>, <code>@Embedded</code> and <code>@Relation</code> here?</p>