title: Xml or Sqlite, When to drop Xml for a Database?
body: <p>I really like Xml for saving data, but when does sqlite/database become the better option? eg, when the xml has more than <em>x</em> items or is greater than <em>y</em> MB?</p>
  
  <p>I am coding an rss reader and I believe I made the wrong choice in using xml over a sqlite database to store a cache of <em>all</em> the feeds items. There are some feeds which have an xml file of ~1mb after a month, another has over 700 items, while most only have ~30 items and are ~50kb in size after a <em>several</em> months. </p>
  
  <p>I currently have no plans to implement a cap because I like to be able to search through everything.</p>
  
  <p>So, my questions are:</p>
  
  <ol>
  <li>When is the overhead of sqlite/databases justified over using xml?</li>
  <li>Are the <strong>few large xml files</strong> justification enough for the database when there are <strong>a lot of small</strong> ones, though even the small ones will grow over time? (a long <em>long</em> time)</li>
  </ol>
  
  <p><strong>updated</strong> (more info)</p>
  
  <p>Every time a feed is selected in the GUI I reload all the items from that feeds xml file.</p>
  
  <p>I also need to modify the read/unread status which seems really hacky when I loop through all nodes in the xml to find the item and then set it to read/unread.</p>