MongoDB is the one I read about. I wasn't trashing them or saying they are hard to set up, just that they are radically different from relational databases.

>There are real differences between the various NoSql dbs, so it's hard to generalize: you need to know what you need for the particular situations.
>
>I wrote an interface to a POS that uses MongoDB to record communication transactions. Very easy to set up.
>
>Of course, if I had the option to write to local VFP Tables it would have been even easier (to get the JSON handling I wanted, in the context of a Web Service client, I opted for Python), easier to install, and easier to review the tables when I needed to. SQLite would have been intermediate in terms of ease of use and ease of looking at data.
>
>Hank
>
>>>>Hmm, I missed the bit about the HTML5 persistent storage PR blitz, is there an executive summary somewhere?
>>>
>>>Google for the decision of Firefox not to support WebSQL and the day job of the committer who
>>>gave them the IndexedDB on BerkelyDB (Hint: who owns it ?)...
>>>I am sooo glad they saved me from the dangers of using a single SQL caching client layer
>>>on the probably most used database tool in the world (which is used in Tunderbird for neraly all stuff)
>>>and try to force me into ORM Key-Value rubbish on disk as well.
>>>
>>>Yuck. Hope many Oracle/SQLServer licenses will be exchanged/saved by going NoSQL in backends
>>>as there is better/more natural support for such structures in browsers now.
>>>
>>>>UPDATE: there seem to be a couple of APIs, "Web SQL Database" and "Indexed Database API". The former seems to be moribund, don't know about the latter. The first articles I've seen about them discuss SQLite rather than MySQL.
>>>>
>>>>Side issue, since you mentioned web-based being "noticeably slower than native apps": I wonder what is considered "fast enough", these days. Years ago I remember hearing that a response time of 2 seconds was considered "fast enough". It's probably faster today. After all, we have a civic duty to reduce car crashes etc. due to inappropriate apping/texting etc. :-/
>>>
>>>Target: 100ms, with outliers falling under 200ms that is for a "reactive app".
>>>Otherwise 1 sec to keep train of thought (or lowered attention span of today's kids).
>>>After 7-10 secs user will work on something else.
>>>Opinioated Source: Google in talks on optimizing GWT JAVA>>JS Compiler and Minifier
>>>
>>
>>Have you done anything with NoSQL? I have read some articles about it in MSDN Magazine and elsewhere and have to admit it's a mind bender for me. Maybe I am just too locked into the SQL way of doing things.