such an update may have to wait for the DB to complete any reads, like while
loading transaction data or even transaction data retrieval. that would lead
to UI freeze
delaying the update has no ill effects, since the data is needed only the next
time the app is run
import android.widget.FilterQueryProvider;
import android.widget.SimpleCursorAdapter;
import android.widget.FilterQueryProvider;
import android.widget.SimpleCursorAdapter;
+import net.ktnx.mobileledger.async.DbOpQueue;
import net.ktnx.mobileledger.async.DescriptionSelectedCallback;
import net.ktnx.mobileledger.model.Data;
import net.ktnx.mobileledger.model.MobileLedgerProfile;
import net.ktnx.mobileledger.async.DescriptionSelectedCallback;
import net.ktnx.mobileledger.model.Data;
import net.ktnx.mobileledger.model.MobileLedgerProfile;
}
static public void setOption(String name, String value) {
debug("option", String.format("%s := %s", name, value));
}
static public void setOption(String name, String value) {
debug("option", String.format("%s := %s", name, value));
- SQLiteDatabase db = MLDB.getDatabase();
- db.execSQL("insert or replace into options(profile, name, value) values(?, ?, ?);",
+ DbOpQueue.add("insert or replace into options(profile, name, value) values(?, ?, ?);",
new String[]{NO_PROFILE, name, value});
}
static public void setLongOption(String name, long value) {
new String[]{NO_PROFILE, name, value});
}
static public void setLongOption(String name, long value) {