Using OrmLite on Android requires more code than it seems like it should. This pull request implements a fairly standard Loader and Adapter to make ormlite easy to use with contemporary Android paradigms like Fragments.

It relies on PR https://github.com/j256/ormlite-core/pull/17 in ormlite-core to facilitate the notification aspect of Android Loaders and Adapters.

Sample app is available here: https://github.com/emmby/ormlite-pr8-sample

I usually use Loaders when populating lists with data, so I've made a couple of Loader implementations for executing queries. There are more ways to query the database in ORMLite, so I'm planning to add more implementations, or maybe find a more generic way to cover all use-cases.

Please let me know if there's anything I can add like unit tests or additional documentation. Thank you.

Hi,

I am encountering this exception which i don't understand.

Caused by: java.lang.IllegalArgumentException: Could not find appropriate get method for private 
java.lang.String com.xx.xx.xx.json.XXX.id

In my XXX pojo, getId method was defined, so i don't understand why this happens, anyone could shed some light on it?

    @DatabaseField(columnName = Table.Columns.ID, id = true, useGetSet = true, unique = true)
    private String id;

    public String getId() {
        return aggregateStart.getTime() + "-" + aggregateEnd.getTime() + "-" + aggregateInterval;
    }

    public void setId(final String id) {
        this.id = id;
    }

is id not allowed as String instead of int? or getId cannot return concatenated string? Thanks!

The following exception has been encountered:

android.database.sqlite.SQLiteException: cannot rollback - no transaction is active (code 1)
    at android.database.sqlite.SQLiteConnection.nativeExecute(Native Method)
    at android.database.sqlite.SQLiteConnection.execute(SQLiteConnection.java:679)
    at android.database.sqlite.SQLiteSession.endTransactionUnchecked(SQLiteSession.java:439)
    at android.database.sqlite.SQLiteSession.endTransaction(SQLiteSession.java:401)
    at android.database.sqlite.SQLiteDatabase.endTransaction(SQLiteDatabase.java:522)
    at com.j256.ormlite.android.AndroidDatabaseConnection.setAutoCommit(SourceFile:77)
    at com.j256.ormlite.misc.TransactionManager.callInTransaction(SourceFile:197)
    at com.j256.ormlite.stmt.StatementExecutor.callBatchTasks(SourceFile:553)
    at com.j256.ormlite.dao.BaseDaoImpl.callBatchTasks(SourceFile:633)
    at com.j256.ormlite.dao.RuntimeExceptionDao.callBatchTasks(SourceFile:534)

ormlite-android:4.48 ormlite-core:4.48 Android: 4.1.2 Only DB operations in Callable are createOrUpdate.

Hi! I receive sometime some error when run application.

java.lang.NullPointerException at com.j256.ormlite.field.FieldType.resultToJava(FieldType.java:819) at com.j256.ormlite.stmt.mapped.BaseMappedQuery.mapRow(BaseMappedQuery.java:60) at com.j256.ormlite.android.AndroidDatabaseConnection.queryForOne(AndroidDatabaseConnection.java:196) at com.j256.ormlite.stmt.mapped.MappedQueryForId.execute(MappedQueryForId.java:38) at com.j256.ormlite.field.FieldType.assignField(FieldType.java:558) at com.j256.ormlite.stmt.mapped.BaseMappedQuery.mapRow(BaseMappedQuery.java:71) at com.j256.ormlite.stmt.SelectIterator.getCurrent(SelectIterator.java:270) at com.j256.ormlite.stmt.SelectIterator.nextThrow(SelectIterator.java:161) at com.j256.ormlite.stmt.StatementExecutor.query(StatementExecutor.java:202) at com.j256.ormlite.stmt.StatementExecutor.queryForAll(StatementExecutor.java:118) at com.j256.ormlite.dao.BaseDaoImpl.queryForAll(BaseDaoImpl.java:241) at com.****.core.database.dao.ShoppingCartDAO.getAll(ShoppingCartDAO.java:199)

I write logic like this guide:: http://habrahabr.ru/post/143431/

The warning Android prints in logcat is: Close cursor android.database.sqlite.SQLiteCursor on null twice or more

SA: http://stackoverflow.com/questions/25245249/ormlite-sqlitecursor-close-cursor-on-null-twice-or-more

Hello, We use the lib in our application. Some company did security review our application. And it found sql injection issue in code of ormlite-android.

Part information from report:

Explanation When carried out against a client-side database, SQL injection can result in the bypassing of authentication/authorization and data corruption or exposure. The impact of a specific SQL injection vulnerability relies on the manner in which the target database is used by the application. Client-side SQL injection is often rated much lower-risk than server-side SQL injection but still may have a profound impact on multi-user applications. Any instance of rawQuery or execSQL that appeared to use format strings or concatentation was flagged by this check. com/j256/ormlite/android/AndroidDatabaseConnection.java : Cursor cursor = this.db.rawQuery("SELECT DISTINCT tbl_name FROM sqlite_master WHERE tbl_name = '" + string + "'", null); Execution Review the application for any locations where dynamic text is used in SQL statements via format strings. Recommendation Use parameterized queries. References OWASP Mobile Top 10 2012-M4 Client Side Injection: https://www.owasp.org/index.php/Mobile_Top_10_2012-M4_Client_Side_Injection

Could you fix the issue ?

hi i used this library and released very well but when i want to save db this error appear Attempt to invoke interface method 'int com.j256.ormlite.dao.Dao.create' plz help me :(

Loaders are supposed to watch for changes to the underlying dataset. Use Dao.registerObserver and Dao.unregisterObserver to start and stop watching for changes.

I have an error "IllegalStateException: attempt to re-open an already-closed object" in multi thread by android 9.0.

I closed the connectionSource in each query. like this:

ConnectionSource cs = cf.getConnectionSource();
try {
    UserDao userDao = new UserDao(cs);
    userDao.deleteAll();
} catch (Exception e) {
    throw e;
} finally {
    try {
        cs.close();
    } catch (SQLException e) {
        logger.error("Exception:" + e);
    }
}

Any ideas?

According to https://developer.android.com/sdk/api_diff/16/changes/android.database.Cursor.html , the Closeable interface was not added until API Level 16.

So the change in 28500b361072ab4c79f7448c32129495aaa279ef causes a runtime exception:

java.lang.IncompatibleClassChangeError: interface not implemented
        at com.j256.ormlite.misc.IOUtils.closeQuietly(IOUtils.java:20)
        at com.j256.ormlite.android.AndroidDatabaseConnection.queryForLong(AndroidDatabaseConnection.java:247)
        at com.j256.ormlite.stmt.StatementExecutor.ifExists(StatementExecutor.java:647)

I discovered this running the ormlite-android from the current master on an Android 4.0.4 phone.

Our Android project uses ormlite-android and depends on another project that uses ormlite-core.

The base dependency includes ormlite with: implementation ("com.j256.ormlite:ormlite-core:6.1")

And the Android project includes ormlite with: implementation ("com.j256.ormlite:ormlite-android:6.1")

When building the Android project, we get the following errors:

> A failure occurred while executing com.android.build.gradle.internal.tasks.CheckDuplicatesRunnable
   > Duplicate class com.j256.ormlite.dao.BaseDaoImpl found in modules ormlite-android-6.1 (com.j256.ormlite:ormlite-android:6.1) and ormlite-core-6.1 (com.j256.ormlite:ormlite-core:6.1)
     Duplicate class com.j256.ormlite.dao.BaseDaoImpl$1 found in modules ormlite-android-6.1 (com.j256.ormlite:ormlite-android:6.1) and ormlite-core-6.1 (com.j256.ormlite:ormlite-core:6.1)
     Duplicate class com.j256.ormlite.dao.BaseDaoImpl$2 found in modules ormlite-android-6.1 (com.j256.ormlite:ormlite-android:6.1) and ormlite-core-6.1 (com.j256.ormlite:ormlite-core:6.1)
     Duplicate class com.j256.ormlite.dao.BaseDaoImpl$3 found in modules ormlite-android-6.1 (com.j256.ormlite:ormlite-android:6.1) and ormlite-core-6.1 (com.j256.ormlite:ormlite-core:6.1)
     Duplicate class com.j256.ormlite.dao.BaseDaoImpl$4 found in modules ormlite-android-6.1 (com.j256.ormlite:ormlite-android:6.1) and ormlite-core-6.1 (com.j256.ormlite:ormlite-core:6.1)
     Duplicate class com.j256.ormlite.dao.BaseDaoImpl$5 found in modules ormlite-android-6.1 (com.j256.ormlite:ormlite-android:6.1) and ormlite-core-6.1 (com.j256.ormlite:ormlite-core:6.1)
     Duplicate class com.j256.ormlite.dao.BaseDaoImpl$6 found in modules ormlite-android-6.1 (com.j256.ormlite:ormlite-android:6.1) and ormlite-core-6.1 (com.j256.ormlite:ormlite-core:6.1)
     Duplicate class com.j256.ormlite.dao.BaseForeignCollection found in modules ormlite-android-6.1 (com.j256.ormlite:ormlite-android:6.1) and ormlite-core-6.1 (com.j256.ormlite:ormlite-core:6.1)
     Duplicate class com.j256.ormlite.dao.CloseableIterable found in modules ormlite-android-6.1 (com.j256.ormlite:ormlite-android:6.1) and ormlite-core-6.1 (com.j256.ormlite:ormlite-core:6.1)
     Duplicate class com.j256.ormlite.dao.CloseableIterator found in modules ormlite-android-6.1 (com.j256.ormlite:ormlite-android:6.1) and ormlite-core-6.1 (com.j256.ormlite:ormlite-core:6.1)
     Duplicate class com.j256.ormlite.dao.CloseableSpliterator found in modules ormlite-android-6.1 (com.j256.ormlite:ormlite-android:6.1) and ormlite-core-6.1 (com.j256.ormlite:ormlite-core:6.1)
     Duplicate class com.j256.ormlite.dao.CloseableSpliteratorImpl found in modules ormlite-android-6.1 (com.j256.ormlite:ormlite-android:6.1) and ormlite-core-6.1 (com.j256.ormlite:ormlite-core:6.1)
     Duplicate class com.j256.ormlite.dao.CloseableWrappedIterable found in modules ormlite-android-6.1 (com.j256.ormlite:ormlite-android:6.1) and ormlite-core-6.1 (com.j256.ormlite:ormlite-core:6.1)
     Duplicate class com.j256.ormlite.dao.CloseableWrappedIterableImpl found in modules ormlite-android-6.1 (com.j256.ormlite:ormlite-android:6.1) and ormlite-core-6.1 (com.j256.ormlite:ormlite-core:6.1)
(...)
com.android.builder.merge.DuplicateRelativeFileException: 2 files found with path 'com/j256/ormlite/core/LICENSE.txt'.

This was working fine with Ormlite 5.x

I have the following code:

public Operation getLocalOperation(int mostRecentOperation, int skip) {

        try {

            Operation operation = databaseHelper.getOperationDao().queryBuilder()
                    .orderBy(Operation.ID_FIELD, true)
                    .offset((long)skip)
                    .where()
                    .isNull(Operation.FOREIGN_USER_FIELD)
                    .and()
                    .ge(Operation.ID_FIELD, mostRecentOperation)
                    .queryForFirst();

            return operation;

        } catch (SQLException e) {

            throw new RuntimeException("Cannot get local operation");
        }
    }

Running this code on Android 30 yields the following exception:

SELECT * FROMOperationsWHERE (ForeignUserIS NULL ANDId>= 0) ORDER BYIdOFFSET 0 LIMIT 1

However, the query fails with the following exception and cause:

Problems executing Android query: SELECT * FROM `Operations` WHERE (`ForeignUser` IS NULL AND `Id` >= 0) ORDER BY `Id` OFFSET 0 LIMIT 1
near "OFFSET": syntax error (code 1 SQLITE_ERROR[1]): , while compiling: SELECT * FROM `Operations` WHERE (`ForeignUser` IS NULL AND `Id` >= 0) ORDER BY `Id` OFFSET 0 LIMIT 1

I'm using com.j256.ormlite:ormlite-android:6.1 on Android 30 (Samsung Galaxy S9+).

now, i have a User object and a Role object , it look like this:

class User {
    private int id;
    private String username;
    private int roleId;
}
class Role {
    private int id;
    private String roleName;
}

i wanna know, how can i serialize it to

 {
    id: 10,
    name: "Jack",
    roleId: 20,
    roleName: "admin"
}

instead of

{
    id: 10,
    name: "Jack,
    role: {
        id: 20,
        roleName: "admin"
    }
}

Hi i was attempting to publish a library that uses this library as a dependency. oss.sonatype.org send me a "lift" report that flagged this library as having a few security related issues. It looks like it's related to log4j 1.x.

Seeing this in the root pom

yes we know this is an issue but it is here for backwards compatibility

As a user of the library, can we exclude the log4j dependency and have the library still be functional? Alternatively, is there a plan to use some other logging library or a newer version?

try { Dao<classExample, Integer> dao = getDao(classExample.class); dao.createIfNotExists(obj); } catch (SQLException e) { e.printStackTrace(); } classExample have string, and if I try to insert an object with single quote ('), then it catch exception. In log, we can see that sql request is using single quote to round string values

Replaced deprecated Android support-v4 library with AndroidX loader library

• Now builds .aar
• Added .aar plugins for maven
• Needs Android SDK (just set $ANDROID_HOME environment variable)