W3C home > Mailing lists > Public > www-tag@w3.org > February 2013

Re: IndexedDB, what were the issues? How do we stop it from happening again?

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Tue, 12 Feb 2013 14:16:33 -0500
Message-ID: <511A9511.5060400@openlinksw.com>
To: www-tag@w3.org
On 2/12/13 12:26 PM, Ashok Malhotra wrote:
> On 2/12/2013 12:02 AM, Kyaw Tun wrote:
>> Advanced query for: SELECT * FROM article WHERE license = 'SA' AND 
>> publisher = 'Nature' ORDER BY 'title'
> It's a good interface to Indexed DB but wouldn't it be easier to just 
> write the query directly?
> That is, using q SQL interface on top of IDB?
> The argument against SQL is complexity but the complexity results from 
> functionality that
> users want.
> Ashok
Isn't that best handled by the WebDB API which is a natural fit for SQL 
RDBMS data sources?

IndexedDB is aligned to Relational DBMS sources in a purer (and lower 
level) sense i.e., high level SQL != Relational DBMS, more of an 
implementation branch (extensional) of the subject matter realm RDBMS 
(which has intensional an extensional [1] [2] :-)


[1] http://en.wikipedia.org/wiki/Datalog .
[2] https://plus.google.com/112399767740508618350/posts/LwEb8ccs8on -- 
coRelational concepts .



Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen

Received on Tuesday, 12 February 2013 19:16:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 12 February 2013 19:16:56 GMT