From 0d7f5b21b997fc4053f8246d72af9480dd6ef7e4 Mon Sep 17 00:00:00 2001 From: Sam Bosley Date: Thu, 23 Feb 2012 11:39:15 -0800 Subject: [PATCH] Use update instead of updateWithOnConflict--it caused an api level error and we want the abort semantics anyways --- api/src/com/todoroo/andlib/data/AbstractDatabase.java | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/api/src/com/todoroo/andlib/data/AbstractDatabase.java b/api/src/com/todoroo/andlib/data/AbstractDatabase.java index 78d06139b..7ab91eae1 100644 --- a/api/src/com/todoroo/andlib/data/AbstractDatabase.java +++ b/api/src/com/todoroo/andlib/data/AbstractDatabase.java @@ -257,8 +257,7 @@ abstract public class AbstractDatabase { * @see android.database.sqlite.SQLiteDatabase#update(String table, ContentValues values, String whereClause, String[] whereArgs) */ public synchronized int update(String table, ContentValues values, String whereClause, String[] whereArgs) { - int result = getDatabase().updateWithOnConflict(table, values, whereClause, whereArgs, - SQLiteDatabase.CONFLICT_FAIL); + int result = getDatabase().update(table, values, whereClause, whereArgs); onDatabaseUpdated(); return result; }