title: best event sourcing db strategy
body: <p>I want to setup a small event sourcing lib.
  I read a few tutorials online, everything understood so far.</p>
  
  <p>The only problem is, in these different tutorials, there are two different database strategies, but without any comments why they use the one they use.</p>
  
  <p>So, I want to ask for your opinion.
  And important, why do you prefer the solution you choose.</p>
  
  <ol>
  <li><p>Solution is the db structure where you create one table for each event.</p></li>
  <li><p>Solution is the db structure where you create only one generic table, and save the events as serialized string to one column.</p></li>
  </ol>
  
  <p>In both cases I'm not sure how they handle event changes, maybe they create a whole new one.</p>
  
  <p>Kind regards</p>