text: And that worked. I mean, of course it worked. It allowed me to search for A and find both results. It also allowed me to search for B and find the person who had it as a second tag.
  I'm not 100% sure I get why the range search was required, but it doesn't feel too entirely wonky to me. For those of you without a modern Firefox, here's a quick screen capture of the display:
  And for those of you want to test, hit the demo button below and enjoy. I apologize if this blog post is a bit confusing. Please feel free to ask any questions, or correct any mistakes.
  To demonstrate power of IndexedDB, I have created a demo app http://dev.yathit.com/demo/... IndexedDB can query several ten thousand records queried under couple of 100ms time using compound index. The query has filters and sorted. For ad-hoc query (without compound index), using key scanning join, it is possible within 4-5 seconds time.
  It seems IndexedDB API expose all possible with WebSQL except no SQL processor there. Performance is much faster than WebSQL.
  All relationships (parent-child, one-to-many, many-to-many) can be model easily and retrived very efficiently.
  So IndexedDB is a way to go, except Safari. I did not see safari teans is active in indexeddb mailing list. It is very likely they are happy with WebSQL and have no interest in IndexedDB API. Only if Google push IndexedDB to webkit code base. It is also a tough thing, since IndexedDB API touch many things like security, performance. I guess webkit code base will not accept easily. just guess.