本文介绍了在Firefox 3.0 +中的SQLite存储的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个支持Firefox 3+的Firefox扩展,SQLite数据库对于我的扩展很重要。我在MDN上看到 API可能会改变,并且解冻,我应该担心呢?

$ b $这个警告可能是过时的,它已经被添加到多年前的文档的原始版本,并且从那以后没有被更新过。事实是,从Firefox 4开始,所有 API都解冻并可能发生变化。但是这不应该是一个担心的理由。随着SQLite访问的进行,API现在看起来已经相当成熟了,Mozilla开发人员大多都在调整性能,而不会引入重大变化。最重要的变化是在Firefox 3.5中引入了异步API,并且弃用了同步API。但是,只要你只使用异步API,你应该是安全的(我不能想象你真的需要支持古老的Firefox 3.0版本,我猜你实际上意味着Firefox 3.6)。

I have a Firefox extension that supports Firefox 3+, and SQLite database is important for my extension. I saw on the MDN that the API might change and it`s "unfrozen", should I be worried about it?

解决方案

This warning is probably outdated, it has been added to the original version of the document years ago and hasn't been updated since. Fact is, starting with Firefox 4 all APIs are unfrozen and could change. But that shouldn't really be a reason to worry. As SQLite access goes, the API seems pretty mature by now and Mozilla developers are mostly tweaking performance without introducing breaking changes. The most important change was the introduction of asynchronous API in Firefox 3.5 and the deprecation of the synchronous API. But as long as you only use asynchronous API you should be on the safe side (I cannot imagine that you really need to support the ancient Firefox 3.0 release, I guess that you actually meant Firefox 3.6).

这篇关于在Firefox 3.0 +中的SQLite存储的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

11-01 05:00