Xml or Sqlite, When to drop Xml for a Database? [closed]

Answer 1

I have made the switch to SQLite and I feel much better knowing it's in a database.

There are a lot of other benefits from this:

• Adding new items is really simple
• Sorting by multiple columns
• Removing duplicates with a unique index

I've created 2 views, one for unread items and one for all items, not sure if this is the best use of views, but I really wanted to try using them.

I also benchmarked the xml vs sqlite using the StopWatch class, and the sqlite is faster, although it could just be that my way of parsing xml files wasn't the fastest method.

1. Small # items and size (25 items, 30kb)
   • ~1.5 ms sqlite
   • ~8.0 ms xml
2. Large # of items (700 items, 350kb)
   • ~20 ms sqlite
   • ~25 ms xml
3. Large file size (850 items, 1024kb)
   • ~45 ms sqlite
   • ~60 ms xml