由网友(俗)分享简介：我目前正在开发一个应用程序，必须创建一个非常大的数据库的潜力。我曾计划上安装的应用程序在SD卡上，允许一些额外的空间。这里最近的交易已经警告我说，这可能不是一个好主意。是否有任何措施，我可以采取以减轻这种行动的危险？还是有什么更好的方法？I'm currently developing an app that has...

我目前正在开发一个应用程序，必须创建一个非常大的数据库的潜力。我曾计划上安装的应用程序在SD卡上，允许一些额外的空间。这里最近的交易已经警告我说，这可能不是一个好主意。是否有任何措施，我可以采取以减轻这种行动的危险？还是有什么更好的方法？

I'm currently developing an app that has the potential to create a very large database. I had planned on installing the app on the SD card to allow for some extra room. Recent dealings here have warned me that that might not be a good idea. Are there any steps I can take to mitigate the danger of this course of action? Or are there any better alternatives?

推荐答案

这是一个com$p$phensive帖子关于这个问题（我不是作者）。

This is a comprehensive post on the subject (I'm not the author).

我认为，整体，它需要传达该SQLite是只是一个SQL机制用于访问文件。似乎目前市场限制是50MB的整个APK。当安装到内存，您需要2倍的APK大小。安装到SD卡只需要规定的APK大小。

I think, overall, it needs to be communicated that SQLite is just a SQL mechanism for accessing a file. It appears that the current market limit is 50mb for the entire APK. When installing to internal memory, you require 2x your APK size. Installing to sdcard requires just the stated APK size.

下面是你将工作对： 1）由于SQLite是只是一个抽象在你的文件，当你做选择，插入，更新等，你会招致SD卡读写成本 2）我见过提到的10000条记录一个软限制的基础上的表现。这篇文章是有点老了，所以它可能变得更好。

Here is what you will be working against: 1.) Since SQLite is just a abstraction over your file, when you do selects, inserts, updates, etc, you will be incurring sdcard read write costs 2.) I've seen mention of a soft limit of 10000 records based on performance. This article is a bit old, so its likely gotten better.

其他然后，你可能会需要设置一些测试，看看什么是可行的。谷歌的搜索走马没有表现出任何的基准日期。

Other then that, you'll probably have to set up some tests to see what is feasible. Cursory search of google did not show any benchmarks to date.