title: SQL: good database design for cards?
body: <p>This is a question about model design for SQL or SQLite.</p>
  
  <p>Suppose you have some card game which has many reusable cards and the players make decks out of those card (e.g. MtG)</p>
  
  <p>Naturally you do not want to make new instances of the cards for every deck that a user might create. That would have a lot of redundancy.</p>
  
  <p>Thus there should be a "master" card (with all of its associated info). </p>
  
  <p>My question is then, how to best integrate the cards (and quantity there of) in a given deck?</p>
  
  <p>(I am not actually making this database, it just highlights the design of having a user having any number collections of multiple items in various quantities from some general stock).</p>