There are a few changes here.

• Bidirectional relationships are handled internally, so the user doesn't have to mark one an inverse anymore or pay attention to that (this was causing lots of problems with one-to-many.) This is done by temporarily caching just the prior Entities that could induce the circular reference. In order to support this, the Primary Key is the first field to be filled when an Entity is loaded.
• One-to-many support. This adds a List TypeMapping, however the only supported list is currently an Entity list.
• Simple order by in DESC.
• Close leaked cursor.

There are a few white-space removals, I apologize for that. My editor auto trims.

On my HTC One I get "Failed to open database" exception all the time. Yet it seems that everything is working fine. How can I get rid of the exception?

I thought ORMDroid can handle one to many relations as :

public class MyObjet extends Entity
{
    // ...
    private ArrayList<MyOtherObject> otherObjects;
}

public class MyOtherObject extends Entity
{
    // ...
}

but not :

com.roscopeco.ormdroid.TypeMappingException: Model MyObjet has unmappable field: public java.util.ArrayList otherObjects

Ross,

My team is testing ORMdroid for use in our project. So far we like what we see.

However, we have encountered an issue when adding fields to an existing Entity. As you probably already know, ORMdroid will throw an Exception when it encounters a field name that does not correspond to the underlying database table.

Ideally, there would be a feature to automatically (or on demand) add new fields to the underlying table as the Entity object expands. I could imagine calling something after initializing the ORMDroidApplication in a new version of the app.

Is there a means of triggering this sort of update in the existing ORMdroid library? If not, my team would be interesting in forking and contributing such a feature...based on any advice you may have.

Thanks, Scott

If there is a Java.util.date property on the entity, "Failed to instantiate model class - does it have a public null constructor?" exception is thrown.

In this case it happened because Entity.load() method swallowed IllegalArgumentExeption and replaced it with ORMDroidException.

catch (Exception e) { throw new ORMDroidException( "Failed to instantiate model class - does it have a public null constructor?", e); }

Perhaps ORMDroidException should at least print e.getClass() for the original exception?

But even then IllegalArgumentExeption does not quite indicate that there was a problem with type serialization. Needs better handling?

On the subject of dates, since util.Date, maybe it is worth serializing it (maybe not)? Azure Mobile Services handles it this way and it works quite well:

https://github.com/WindowsAzure/azure-mobile-services/blob/master/sdk/android/src/sdk/src/com/microsoft/windowsazure/mobileservices/DateSerializer.java

Issue 1: When I have only one field except a dummy id field in my Entity extended class, query used to have a tailing comma.

Fix File Entity.java

+    private String stripTrailingComma(String string) {
+      // check for last comma
+      if (string.endsWith(",")) {
+        return string.substring(0, string.length() - 1);
+      }
+      return string;
+    }
+
+    int insert(SQLiteDatabase db, Entity o) {
-      String sql = "INSERT INTO " + mTableName + " (" +getColNames()
-          + ") VALUES (" + getFieldValues(db, o)+ ")";
+      String sql = "INSERT INTO " + mTableName + " (" + stripTrailingComma(getColNames())
+          + ") VALUES (" + stripTrailingComma(getFieldValues(db, o))+ ")";

Issue 2: Cursor not closed while executing multiexecute query

Fix File Entity.java

        /*
         * Moves cursor to start, and runs through all records.
         */
        <T extends Entity> List<T> loadAll(SQLiteDatabase db, Cursor c) {
            ArrayList<T> list = new ArrayList<T>();

            if (c.moveToFirst()) {
                do {
                    list.add(this.<T> load(db, c));
                } while (c.moveToNext());
            }
+                       c.close();

            return list;
        }

I have downloaded the sample from http://orm-droid.googlecode.com/svn/trunk/ORMSample I am getting and error with the following method in Person class.

public List people() { return query(Person.class).where("department").eq(id).executeMulti(); }

The argument for where is invalid because its expecting type com.roscopeco.ormdroid.SQLExpression while the passed argument is String.

Same error is present in the activity classes,when calling the where method

Please advise me how to fix this

I'm getting the following exception, although I'm not sure if ormdroid's causing it. All I know is that I'm referencing Entitys in my code when it happens.

12-17 17:48:57.155     847-1466/? E/DatabaseUtils﹕ Writing exception to parcel
    java.lang.SecurityException: Permission Denial: get/set setting for user asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL
            at com.android.server.am.ActivityManagerService.handleIncomingUser(ActivityManagerService.java:13090)
            at android.app.ActivityManager.handleIncomingUser(ActivityManager.java:2038)
            at com.android.providers.settings.SettingsProvider.callFromPackage(SettingsProvider.java:607)
            at android.content.ContentProvider$Transport.call(ContentProvider.java:279)
            at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:273)
            at android.os.Binder.execTransact(Binder.java:388)
            at dalvik.system.NativeStart.run(Native Method)

To test your library, I made a simple test : I created a class Man extends Person extends Entity. When I try to load all Person in DB, only the Person table is loaded. I was expecting that Man table would also be returned.

Entity.query(Person.class).executeMulti();

Am I doing something wrong ?

Not sure if it is a bug, but an enhancement :D

From that, awesome job guys !

android frequently uses int/string constants instead of enum's.. .attempting any setting of these causes expected errors.

ex

public class User{ public final static int USER_TYPE_ADMIN = 0; public final static int USER_TYPE_SUPERADMIN=1;

public int userType;

}

I had to move the constants out into another class, then deserializing from db worked properly again.

Perhaps we should ignore, or if we can access protection levels and whether or not its static / non-static, we should automatically ignore said fields? (we'll never be able to set a static var like the actual USER_TYPE_ADMIN in this case).

Otherwise we could put together an ignore annotation for explicit ignoring.

I noticed, that mTransient is not reset to true, if I call delete() on an Entity from database. I'm not sure if this has any deeper reason, but I think this may cause some unexpected behavior - at least it did for me.

good morning how are you

I have tried the library, and it works fine, but I want to change the path of the database, there is some way to do it, excellent work, thanks

Exception Fatal Exception: java.lang.RuntimeException Unable to start activity ComponentInfo{ }: java.lang.IllegalStateException: Couldn't read row 0, col 18 from CursorWindow. Make sure the Cursor is initialized correctly before accessing data from it.

Problem is caused where executeMulti, is an random errror.

Are you thinking about implementing a way to be able to upgrade/migrate the database ?

I see 2 ways :

• Adding Version in Manifest and a script in assets to allow manual migration
• Adding Version in Manifest and checking Tables programmatically at the app init

Of course, there are other ways to do that. What are your thoughts about it @roscopeco ?

What if I want to use the same ids used in my server ? I create a Entity instance specifying my own id, then I save it, ORMDroid throws away my own id and replaces it by last_insert_rowid. I'm stuck there. I think I have to create a new field, like cloudId, and use this one when manipulating Entities... Is there any other work around ?

Thanks !