Re: 'Pure' client-side javscript database?

Jim Davis wrote:
> "Richard Cornford" <Richard@litotes.demon.co.uk> wrote in message
> news:deqovc$sbr$1$8300dec7@news.demon.co.uk...
>
>>cjl wrote:
>>
>>>I know that it is silly in the age of Google to 'lose' something on
>>>the internet, but I recently checked out a project that had
>>>implemented a database with a subset of SQL in pure client-side
>>>javascript.
>>
>>A client-side database? Now there is a spectacularly bad idea. The last
>>thing you want to do is have the client download an entire database just
>>so it can extract a tiny part of it. Server-side is where the database
>>belongs, and where the task of extracting data from it should happen.
>
>
> Although I agree with you in general I think there are many scenarios where
> this could be useful. It really depends on the data in question and the
> circumstances of its use, I think.

You raise some interesting scenarios, but in how many of those would you
use SQL to extract and format data from the database/cache rather than
use purpose built routines?

The concept of building a client-side database and SQL-based API is an
interesting exercise, but it's unlikely to have any real use. The main
purposes of SQL are standardisation of a query interface and portability
between database implementations, neither of which seem to be problems
worth fixing in a client-side JavaScript database.

[...]

-- 
Rob