Home/ Questions/Q 7981335
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T10:20:18+00:00

I’m starting with Android and wonder if background Task like DB reading and saving

  • 0

I’m starting with Android and wonder if background Task like DB reading and saving are always encapsulated in private classes?

I mean, at the moment I have:

private class SaveToDB extends AsyncTask..
private class ReadFromDB extends AsyncTask..

public void onButtonClick(View v) {
 new SaveToDB().execute();
}

And so on. This way, I always have to create a new object if I want to execute background tasks. Is that the correct way?

What I wonder is that all my private classes are “actions” itself, not really objects. As they are named eg save or read which naming normally applies to methods by convention, not to classes.

Moreover, in case I’m doing it right: is it good practice to neast the private classes inside MyApplication Activity? Or should I refacter them out into own separate classes?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If you are firing of async tasks to interact with a sqlite database, then its not the best way to do things these days, you should check out cursor loaders instead.

    http://developer.android.com/guide/topics/fundamentals/loaders.html

    http://developer.android.com/reference/android/content/CursorLoader.html

    Once you got your head around them they are much easier than firing off async tasks, infact they build on top of async tasks to address some of the issues you describe and are tolerant to configuration changes.

    I highly recommend to move away from AsyncTask (for db access) and use the Loader API instead.

    Its backported in the compatibility package so you can use them in older versions prior to Honeycomb.

    • 0