blocks|key|1388206|text|我认为放弃IndexedDB是个坏主意，因为它可能是未来的格式，所以Safari可能不再支持WebSQL。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1388207|似乎有各种各样的JavaScript解决方案来弥补两种储蓄之间的差距，无论用户浏览器上有哪一种：JavaScript库将IndexedDB和WebSQL连接起来，我认为这可能是最好的解决方案。|offset|length|1388208|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/6116053/javascript-library-to-bridge-indexeddb-and-websql^0|0|1C|W|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

I think abandoning IndexedDB would be a bad idea, because it's probably the format of the future, so Safari might stop supporting WebSQL.

It appears there are various JavaScript solutions to bridge the gap between the two - saving in whichever is available on the user's browser:
<a href="https://stackoverflow.com/questions/6116053/javascript-library-to-bridge-indexeddb-and-websql">JavaScript Library to Bridge IndexedDB and WebSQL</a>
I think this is probably your best solution.

blocks|key|1864461|text|IndexedDB很可能是未来受支持的数据库，最好使用它而不是WebSQL。正如雷蒙德所指出的，最好参考http://www.caniuse.com来查看桌面浏览器和移动浏览器中当前/未来的支持。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1864462|根据您的解决方案的当前需求，您可以使用使用JavaScript并提供查询接口的许多可用的局部存储库之一。其中一个对我很有用的库是劳恩椅。|1864463|entityMap|0|LINK|mutability|MUTABLE|url|http://www.caniuse.com/|1|https://en.wikipedia.org/wiki/Web_storage#Local_and_session_storage|2|http://brian.io/lawnchair/^0|1G|M|0|0|18|4|1|1S|3|2|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]|$A|Z|B|10|1|11]]|C|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]]]

IndexedDB is most likely the supported database of the future and it would be best to go with that instead of WebSQL. As Raymond pointed, it is best to refer to <a href="http://www.caniuse.com" rel="nofollow">http://www.caniuse.com</a> to see the current/future support in both desktop and mobile browsers. 

Depending on the current needs of your solution, you might be fine with one of the many JavaScript libraries that are available which use the <a href="https://en.wikipedia.org/wiki/Web_storage#Local_and_session_storage" rel="nofollow">local storage</a> and provide a query interface. One of the libraries, which has worked well for me is <a href="http://brian.io/lawnchair/" rel="nofollow">Lawnchair</a>.

blocks|key|1388239|text|是的，IndexedDB+API是伟大的，所有浏览器都将在不久的将来支持。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1388240|我绝对推荐我自己的解决方案https://bitbucket.org/ytkyaw/ydn-db，它是非常薄的包装IndexedDB和回到Sqlite。|offset|length|1388241|entityMap|0|LINK|mutability|MUTABLE|url|https://bitbucket.org/ytkyaw/ydn-db^0|0|D|Z|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Yes, IndexedDB API is great and all browsers will support in near future.

I definitely recommend my own solution <a href="https://bitbucket.org/ytkyaw/ydn-db">https://bitbucket.org/ytkyaw/ydn-db</a> it is very thin wrapper for IndexedDB and fall back to Sqlite for safari.

blocks|key|924492|text|这可能已经很晚了，但是你可以看看：SequelSphere|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|924493|它是一个100%25+HTML5+5/JavaScript关系数据库，跨浏览器工作，并使用本地存储来持久化其数据。您也可以使用SQL查询它。它是自己的数据库引擎，不依赖于内置(WebSQL)关系数据库。因此，它将在所有浏览器上工作。|924494|虽然它目前只支持localStorage，但它的想法是支持未来的所有标准。由于浏览器支持其他类型的持久性，SequelSphere将利用这一点。积极的是，您只使用标准的SequelSphere编写代码，并让它处理持久化。|924495|尽管如此，请注意，这是一个新产品的市场，因此，这与积极和消极。|924496|entityMap|0|LINK|mutability|MUTABLE|url|http://www.sequelsphere.com/^0|H|C|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

This may be late to the game, but you could look at: <a href="http://www.sequelsphere.com" rel="nofollow">SequelSphere</a>

It is a 100% HTML5/JavaScript Relational Database that works cross-browser and uses local storage to persist it's data. You can use SQL to query it as well. It is it's own database engine, and doesn't rely upon the built-in (WebSQL) relational databases. As such, it will work across all browsers.

While it currently only supports localStorage, the idea is to support all the standards going forward. As browsers support other types of persistence, SequelSphere would take advantage of that. The positive is that you only code against SequelSphere using standard SQL, and let it handle the persistence.

Nevertheless, be aware that it is a new product to the market, so that comes with both positives and negatives.

blocks|key|1864587|text|首先，W3C反对的是WebSQL而不是SQLite|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1864588|IndexedDB+-|1864589|它与多种类型的移动操作系统不兼容，只与某些类型的移动操作系统兼容。|unordered-list-item|1864590|开发人员不能在IndexedDB中使用SQL。他们可以用SQLite和WebSQL|1864591|大多数开发人员都尽量避免使用IndexedDB。|1864592|WebSQL+-|1864593|它已被W3C否决，这意味着它不再被维护或开发。|1864594|它需要另一个名为poly填充的插件，以使移动应用程序能够与流行的移动操作系统(如Google和Apple+iOS+)一起工作。|1864595|SQLite+-|1864596|它得到了谷歌的奖励。|1864597|SQLite有自己的官方网站。IndexedDB和WebSQL没有|1864598|在谷歌上，SQLite返回了430万个结果。WebSQL返回略小于700+K的结果，IndexedDB返回282+K结果。|1864599|如果你想要一个关于SQLite的快速教程，|1864600|利用Android和Phonegap存储SQLite数据库|offset|length|1864601|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/19570868/storage-of-sqlite-database-using-android-and-phonegap/25518453#25518453^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|T|0|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1D|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1E|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|1F|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|1G|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1H|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|1I|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|1J|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1K|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|1L|8|@]|9|@]|A|$]]|$1|U|3|V|5|F|7|1M|8|@]|9|@]|A|$]]|$1|W|3|X|5|F|7|1N|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1O|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1P|8|@]|9|@$12|1Q|13|1R|1|1S]]|A|$]]|$1|14|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]]|15|$16|$5|17|18|19|A|$1A|1B]]]]

First of all, the one that has been deprecated by W3C is WebSQL not SQLite

IndexedDB -

<ul>
<li>It is incompatible with many types of mobile OS and is only compatible with certain types of versions of mobile OS</li>
<li>Developers cannot use SQL with IndexedDB. They can with SQLite and WebSQL</li>
<li>Most developers actively avoid using IndexedDB as much as they can</li>
</ul>

WebSQL -

<ul>
<li>It has been deprecated by W3C which means it is no longer maintained or developed</li>
<li>It requires another plugin called Polyfill to enable mobile applications to work with popular mobile OS such as Google Android and Apple iOS</li>
</ul>

SQLite -

<ul>
<li>It received an award from Google </li>
<li>SQLite has its official website. IndexedDB and WebSQL do not</li>
<li>On Google, SQLite returns 4.3 million results. WebSQL returns a bit less than 700K results and IndexedDB returns 282K results. </li>
</ul>

If you want a quick tutorial on SQLite, 

<a href="https://stackoverflow.com/questions/19570868/storage-of-sqlite-database-using-android-and-phonegap/25518453#25518453">Storage of SQLite database using Android and Phonegap</a>

blocks|key|924546|text|如果不想在IndexedDB或WebSQL之间进行选择，可以使用Javascript库PouchDB。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|924547|我在中使用它来存储离线数据，它运行得很好。如果没有可用的internet连接，则将数据存储在本地数据库(使用IndexedDB或WebSQL)上，并且在存在可用连接时与远程数据库(CouchDB数据库)同步。|924548|PouchDB将依赖于IndexedDB，但如果不支持IndexedDB，则依赖于回到WebSQL。此外，还可以为Cordova/PhoneGap使用SQLite插件。|924549|entityMap|0|LINK|mutability|MUTABLE|url|http://pouchdb.com/|1|http://couchdb.apache.org/|2|http://pouchdb.com/adapters.html#pouchdb_in_the_browser^0|17|7|0|0|2I|7|1|0|15|8|2|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|F|3|G|5|6|7|11|8|@]|9|@$A|12|B|13|1|14]]|C|$]]|$1|H|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]|R|$5|K|L|M|C|$N|S]]]]

If you don't want to choose between IndexedDB or WebSQL you can use the Javascript library <a href="http://pouchdb.com/" rel="nofollow">PouchDB</a>.

I use it in an Android Webview to store offline data and it works pretty well. The data are stored on a local database (using IndexedDB or WebSQL) if there is no internet connection available and is synchronized with a remote database (<a href="http://couchdb.apache.org/" rel="nofollow">CouchDB</a> database) when there is an available connection.

PouchDB will depend on IndexedDB but <a href="http://pouchdb.com/adapters.html#pouchdb_in_the_browser" rel="nofollow">fall back to WebSQL</a> if IndexedDB is not supported. There is also the possibility to use a SQLite plugin for Cordova/PhoneGap.

blocks|key|1388471|text|我想做一个小编辑来更新这个问题，因为如果您对websql、localStorage和indexedDB这一主题进行了研究，谷歌将向我们介绍这个问题。编辑被拒绝了，所以我张贴作为一个答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1388472|正如其他人在回答中指出的那样，IndexedDB在支持和web内容方面缺乏一点支持，因为它的文档和规范是不够的。|1388473|但IndexedDB支持一直是极大地改进了移动。它的进步如此之大，以至于唯一没有任何支持的浏览器就是Opera+Mini，但它只占市场使用量的0.34%25。。|offset|length|1388474|从2015年起，我建议任何开发人员迁移到IndexedDB，因为WebSQL已经被废弃，IE和Firefox不再支持它(仅这一项就占了市场使用量的15%25以上！)SQLite正在迅速地输给IndexedDB，后者现在已经拥有了很好的文件来源，许多。还有一些官员!.一些IT公司甚至也在鼓励使用，比如IBM。|1388475|我要使用它，到目前为止我还没有遇到任何问题。Safari增加了对它的支持，以及所有主要的浏览器。勇敢点儿!|1388476|编辑:个人增编:我尝试了IndexedDB。我是我团队中的一名高级成员，对于小的存储问题，IndexedDB语法太混乱和复杂--我结束了使用本地存储来保存一些简单的JSON数据，并在需要的时候解析它。让我的团队中的任何人都能得到它更好(当然我也是！)|1388477|entityMap|0|LINK|mutability|MUTABLE|url|http://caniuse.com/#search=indexed|1|http://caniuse.com/usage-table|2|https://msdn.microsoft.com/en-us/library/hh673548%2528v=vs.85%2529.aspx?f=255&MSPPError=-2147217396|3|https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API|4|http://www.w3.org/TR/IndexedDB/|5|http://www.ibm.com/developerworks/library/wa-indexeddb/^0|0|0|F|8|0|1P|G|1|0|37|4|2|3C|2|3|3F|6|4|44|3|5|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|17|8|@]|9|@$F|18|G|19|1|1A]|$F|1B|G|1C|1|1D]]|A|$]]|$1|H|3|I|5|6|7|1E|8|@]|9|@$F|1F|G|1G|1|1H]|$F|1I|G|1J|1|1K]|$F|1L|G|1M|1|1N]|$F|1O|G|1P|1|1Q]]|A|$]]|$1|J|3|K|5|6|7|1R|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1S|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]|V|$5|Q|R|S|A|$T|W]]|X|$5|Q|R|S|A|$T|Y]]|Z|$5|Q|R|S|A|$T|10]]|11|$5|Q|R|S|A|$T|12]]|13|$5|Q|R|S|A|$T|14]]]]

I wanted to make a small edit to update this question, as google is directing to us to this question if you make a research on the subject of websql, localStorage and indexedDB. The edit was rejected, so I'm posting as a answer.

As others stated in their answers, IndexedDB lacked a bit before on support and on content on the web for it's documentation and specification.

But IndexedDB support has been <a href="http://caniuse.com/#search=indexed" rel="nofollow">vastly improved for mobile</a>. It improved so much that the only browser who has no support or whatsoever, is Opera Mini, <a href="http://caniuse.com/usage-table" rel="nofollow">but it has only 0,34% of market usage</a>.

As of 2015, I would suggest any developer to move to IndexedDB, as WebSQL has been deprecated and IE and Firefox stopped supporting it (that's more than 15% of market usage for these alone!) and SQLite is losing space rapidly to IndexedDB, which have now really good <a href="https://msdn.microsoft.com/en-us/library/hh673548%28v=vs.85%29.aspx?f=255&amp;MSPPError=-2147217396" rel="nofollow">documentation sources</a>, <a href="https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API" rel="nofollow">many</a>. <a href="http://www.w3.org/TR/IndexedDB/" rel="nofollow">Some official as well</a>!. Some IT companies are even motivating usage as well, like <a href="http://www.ibm.com/developerworks/library/wa-indexeddb/" rel="nofollow">IBM</a>.

I'm going to use it, and I have not met any problems so far. Safari has added support to it, and all major browsers as well. Go for it!

EDIT: A personnal addendum: I tried IndexedDB. I'm a Senior on my team, and IndexedDB syntax is just too messy and complex for small storage problems - I ended using localstorage to save some simple JSON data and parsing it when I need it. Way better for anyone on my team to get it (Me as well, of course!)

blocks|key|926435|text|正如其他人所指出的，自从提出这个问题以来，webSQL+已经被废弃了，而IndexedDB实现了现在存在于所有主要的浏览器供应商中。。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|926436|因此，对于那些可能发现自己在这里面临着同样的决策的人，请与IndexedDB一起去吧。|926437|这里的其他人也正确地暗示，不必在这两种类型的数据库之间做出选择。您可以简单地选择(或制作)一个库，它利用客户机上可用的任何数据库。|926438|如果您正在寻找这样一个库，请查看BakedGoods。它建立了一个统一的接口，可用于在所有本机存储设备和一些非本地客户端存储设备中执行存储操作。它还保持了每个用户所提供的灵活性和选项。|926439|使用它，在支持的任何数据库类型中执行存储操作是一个问题。|926440|..。为这两种数据库类型指定适当的操作选项和等效信任：|926441|//If+the+operation+is+a+set(),+and+the+referenced+structures+
//don't+exist,+they+will+be+created+automatically.

var+webSQLOptionsObj+=+{
++++databaseName:+"Example_DB",
++++databaseDisplayName:+"Example+DB",
++++databaseVersion:+"",
++++estimatedDatabaseSize:+1024+*+1024,
++++tableData:+{
++++++++name:+"Main",
++++++++keyColumnName:+"lastName",
++++++++columnDefinitions:+"(lastName+TEXT+PRIMARY+KEY,+firstName+TEXT)"
++++},+
++++tableIndexDataArray:+[name:+"First_Name_Index",+columnNames:+"(firstName)"]
};

var+indexedDBOptionsObj+=+{
++++databaseName:+"Example_DB",
++++databaseVersion:+1,
++++objectStoreData:+{
++++++++name:+"Main",
++++++++keyPath:+lastName,
++++++++autoIncrement:+false
++++},
++++objectStoreIndexDataArray:+[
++++++++{name:+"First_Name_Index",+keyPath:+"firstName",+unique:+false,+multiEntry:+false}
++++],
};

var+optionsObj+=+{
++++conductDisjointly:+false,+
++++webSQL:+webSQLOptionsObj,+
++++indexedDB:+indexedDBOptionsObj
};|code-block|syntax|javascript|926442|..。并进行行动：|926443|bakedGoods.set({
++++data:+[
++++++++{value:+{lastName:+"Obama",+firstName:+"Barack"}},+
++++++++{value:+{lastName:+"Biden",+firstName:+"Joe"}}
++++],
++++storageTypes:+["indexedDB",+"webSQL"],
++++options:+optionsObj,
++++complete:+function(byStorageTypeStoredItemRangeDataObj,+byStorageTypeErrorObj){}
});|926444|它的简单接口和无与伦比的存储设施支持是以缺乏对某些存储设备特定配置的支持为代价的。例如，它不支持在具有多列主键的WebSQL表中执行存储操作。|926445|因此，如果您大量使用这些类型的特性，您可能会想看看其他地方。|926446|哦，为了完全透明，BakedGoods是由这个家伙维护的:)。|926447|entityMap|0|LINK|mutability|MUTABLE|url|http://caniuse.com/#search=websql|1|http://caniuse.com/#search=indexeddb|2|https://github.com/klawson88/Baked-Goods^0|S|6|0|1C|I|1|0|0|0|G|A|2|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1E|8|@]|9|@$A|1F|B|1G|1|1H]|$A|1I|B|1J|1|1K]]|C|$]]|$1|D|3|E|5|6|7|1L|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1M|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|1N|8|@]|9|@$A|1O|B|1P|1|1Q]]|C|$]]|$1|J|3|K|5|6|7|1R|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|1S|8|@]|9|@]|C|$]]|$1|N|3|O|5|P|7|1T|8|@]|9|@]|C|$Q|R]]|$1|S|3|T|5|6|7|1U|8|@]|9|@]|C|$]]|$1|U|3|V|5|P|7|1V|8|@]|9|@]|C|$Q|R]]|$1|W|3|X|5|6|7|1W|8|@]|9|@]|C|$]]|$1|Y|3|Z|5|6|7|1X|8|@]|9|@]|C|$]]|$1|10|3|11|5|6|7|1Y|8|@]|9|@]|C|$]]|$1|12|3|-4|5|6|7|1Z|8|@]|9|@]|C|$]]]|13|$14|$5|15|16|17|C|$18|19]]|1A|$5|15|16|17|C|$18|1B]]|1C|$5|15|16|17|C|$18|1D]]]]

As other have pointed out, since this question has been asked, webSQL <a href="http://caniuse.com/#search=websql" rel="nofollow">has been deprecated</a>, while IndexedDB implementations <a href="http://caniuse.com/#search=indexeddb" rel="nofollow">now exist in all of the major browser vendors</a>.

So to anyone who may find themselves here faced with the same decision to make, go with IndexedDB.

Others here have also implied, correctly, that a choice doesn't have to be made between the two types of databases. One can simply choose (or make) a library which utilizes whichever database is available on a client machine.

Check out <a href="https://github.com/klawson88/Baked-Goods" rel="nofollow">BakedGoods</a> if you're looking for such a library. It establishes a uniform interface that can be used to conduct storage operations in all native, and some non-native client storage facilities. It also maintains the flexibility and options afforded to the user by each.

With it, conducting storage operations in whichever of the database types is supported is a matter of...

... specifying the appropriate operation options and equivalent configs for both database types:

<pre><code>//If the operation is a set(), and the referenced structures 
//don't exist, they will be created automatically.

var webSQLOptionsObj = {
 databaseName: "Example_DB",
 databaseDisplayName: "Example DB",
 databaseVersion: "",
 estimatedDatabaseSize: 1024 * 1024,
 tableData: {
 name: "Main",
 keyColumnName: "lastName",
 columnDefinitions: "(lastName TEXT PRIMARY KEY, firstName TEXT)"
 }, 
 tableIndexDataArray: [name: "First_Name_Index", columnNames: "(firstName)"]
};

var indexedDBOptionsObj = {
 databaseName: "Example_DB",
 databaseVersion: 1,
 objectStoreData: {
 name: "Main",
 keyPath: lastName,
 autoIncrement: false
 },
 objectStoreIndexDataArray: [
 {name: "First_Name_Index", keyPath: "firstName", unique: false, multiEntry: false}
 ],
};

var optionsObj = {
 conductDisjointly: false, 
 webSQL: webSQLOptionsObj, 
 indexedDB: indexedDBOptionsObj
};
</code></pre>

... and conducting the operation:

<pre><code>bakedGoods.set({
 data: [
 {value: {lastName: "Obama", firstName: "Barack"}}, 
 {value: {lastName: "Biden", firstName: "Joe"}}
 ],
 storageTypes: ["indexedDB", "webSQL"],
 options: optionsObj,
 complete: function(byStorageTypeStoredItemRangeDataObj, byStorageTypeErrorObj){}
});
</code></pre>

Its simple interface and unmatched storage facility support comes at the cost of lack of support for some storage facility-specific configurations. For instance, it does not support the conduction of storage operations in WebSQL tables with multi-column primary keys. 

So if you make heavy use of those types of features, you may want to look elsewhere.

Oh, and for the sake of complete transparency, BakedGoods is maintained by this guy right here :) .

I am in the R&amp;D phase of developing an application, with the following key requirements:

<ul>
<li>HTML5 <a href="http://en.wikipedia.org/wiki/Web_application" rel="noreferrer">web application</a> - which will also have a hybrid version</li>
<li>Forms data will be stored locally, when no Internet connection</li>
</ul>

I cannot use web storage due to quota limitations - I am comparing <a href="http://en.wikipedia.org/wiki/SQLite" rel="noreferrer">SQLite</a> and <a href="https://en.wikipedia.org/wiki/Indexed_Database_API" rel="noreferrer">Indexed DB</a>.

<ul>
<li>SQLite seems to be best fit, but it is deprecated</li>
<li>Indexed DB is a good alternative, but there's no <a href="http://en.wikipedia.org/wiki/Safari_%28web_browser%29" rel="noreferrer">Safari</a> support - A hybrid application is supposed to be run on the iPad and on an Android device in the future.</li>
</ul>

I am confused in the selection of API. Is there some other alternative to SQLite or support of Indexed DB expected on Safari?

Offline access - SQLite or Indexed DB?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正处于开发应用程序的研发阶段，主要要求如下：HTML5  -它也将有一个混合版本当没有互联网连接时，表单数据将在本地存储由于配额限制，我不能使用web存储--我在比较和。SQLite似乎是最合适的，但它被废弃了。索引DB是一个很好的选择，但是没有支持--未来混合应用程序应该在iPad和安卓设备上运行。我对API的选择...

问离线访问- SQLite还是索引DB？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问离线访问- SQLite还是索引DB？EN