- From: Aaron Powell <me@aaron-powell.com>
- Date: Thu, 11 Apr 2013 12:33:23 +0000
- To: Rob VonNesselrode <Rob_VonNesselrode@sitechcs.com>, "public-webapps@w3.org" <public-webapps@w3.org>
Received on Thursday, 11 April 2013 12:33:52 UTC
But there is a query language, you've got indexes, bi-directional cursors, ranges, etc. Admittedly it's not a "Select * from ... " syntax but to me that would seem foreign on the web anyway. Constructing and executing an object model is more consistent with the other standards in the browser such as DOM interaction or the event model. Keep in mind that IndexedDB is very low level and provides the building blocks for library authors to provide the 'syntax sugar' as it were on top that better suites the way they want to/believe the API should be interacted with. My 2c on the matter anyway. Aaron Powell MVP - Internet Explorer (Development) | FunnelWeb Team Member<http://funnelweblog.com/> http://apowell.me<http://apowell.me/> | http://twitter.com/slace | Skype: aaron.l.powell | Github<http://github.com/aaronpowell/> | BitBucket<http://hg.apwll.me/> From: Rob VonNesselrode [mailto:Rob_VonNesselrode@sitechcs.com] Sent: Thursday, 11 April 2013 11:54 AM To: public-webapps@w3.org Subject: What will be the query language for IndexedDb By all means take away WebSQL the database but you should then add SQL (the query language) to whatever you put in its place Without a standardised query language a data store is, well, just a bucket of bits. Whether it is "human readable", key-value paired or not Regards Rob von Nesselrode
Received on Thursday, 11 April 2013 12:33:52 UTC