2

I have a database from where i need to extract quite a lot of data. Now i get that data when required, i.e. I have made a class that handles database interactions and whenever an activity requires data it will call that class for the data. So at a time an Activity only has the bare minimum amount of data in memory (i.e. the data that it is using). But everytime i change an activity i have to perform database access to fetch data for the new activity.

Method 2

As opposed to this i have this other alternative, in which i make an application object and then perform database access in the beginning and then store all the data that i would require (in all the activities) in the application object. Whenever i need the data, i refer to the application object. The downside of this that i will be holding too much extra data that i am not using at a given instant.

Which of the above 2 approaches is better?

Thank you in advance.

user590849
  • 11,655
  • 27
  • 84
  • 125

2 Answers2

0

It depends on your requirements and their priorities. If the time required for solution 2 is too long for you to accept then optimize (e.g. by using method 2, but in general I would advise against storing potentially all of your database in memory ... assuming the amount of memory will suffice).

Did you try solution 1. If the problem is only to read the data from database, it should not take too long to load the data for one activity. If complex calculations are involved you might be pressed to optimize. But don't optimize just in case!

Stefan
  • 4,645
  • 1
  • 19
  • 35
  • thanks for the answer. My database operations are quite mundane.. they don't require much operation. I am more inclined to option 1. It seems more efficient. – user590849 Feb 01 '12 at 12:30
  • As I said, if method 1 is good enough in terms of time for a select, definitely do not implement method 2. – Stefan Feb 01 '12 at 12:39
0

I prefer the first approach because making a call to database is not costly until and unless it is being accessed by multiple applications.

Sai Mukesh
  • 401
  • 4
  • 11