I recently got this question in an audit: How to work with big databases (more GB) on android?
I can understand how it might be closed as Not Constructive -- opinions will differ as to whether one should even attempt a 10GB database on a typical Android device, and the right answer depends in part on exactly what device we're talking about. But it also seems possible to come up with a constructive answer even without changing the question. For example:
SQLite can handle databases of that size given the right hardware, but Android runs on a variety of devices, not all of which are really up to the task. You'll need to do some testing with a similar database on your target device to determine if you can get acceptable performance. You can get an idea of whether it makes sense to pursue this app by loading your database file into SomeDatabaseApp, available in the Android Market. If that works out, write a little test app of your own to help you collect some metrics and give you a baseline for your apps performance. This will give you some hard data upon which to base your answer to your client. Some techniques for dealing with the small cursor problem are...
I'm not necessarily trying to make a case for reopening the question, but I'm not convinced that its so obviously Not Constructive that it makes a good audit question. Am I missing something?