title: How can I make a better model of one column tables?
body: <p>I am writing an application where I have a table to store different kinds of Assets, each asset has a Brand and each brand has N number of Models. Problem is I only need to store the names of the different brands and models and it doesn't seems right to me to have two different tables with just one column each to store this. Is there a better way to model this? </p>
  
  <p>This is what the ER diagram of that part of my app looks like at the moment:</p>
  
  <p><img src="https://i.stack.imgur.com/0TjbS.png" alt="ER Diagram"></p>