1. is SQL overkill? 2. is SQL db configured optimally? 3. are SQL queries executed asynchronously?

This now only applies to Android since bug 853549 switched to JSON for desktop.

(In reply to Matthew N. [:MattN] (away until Jan. 7) from comment #1) > This now only applies to Android since bug 853549 switched to JSON for > desktop. Whoa, can we do that for Android, too? I would think the main difficulty would be sync, since we use SQLite in a content provider for that.

(In reply to :Margaret Leibovic from comment #2) > (In reply to Matthew N. [:MattN] (away until Jan. 7) from comment #1) > > This now only applies to Android since bug 853549 switched to JSON for > > desktop. > > Whoa, can we do that for Android, too? I would think the main difficulty > would be sync, since we use SQLite in a content provider for that. Oh, it looks like bug 946857 already has some relevant discussion.

Yeah, if we make any changes here (and I think we should), it'll be one or both of two things: * Switching to a JSON backend like desktop, not porting to mozStorage. * Moving to a Java-side storage mechanism (probably a JSON-backed ContentProvider, which will make Bug 1098501 much easier), which is Bug 946857. So I'm gonna resolve this with some pointers.