How can I delete all the data in one table?

new Delete().from(Car.class).execute(); Gives me a "java.lang.IllegalArgumentException: Empty bindArgs".

EDIT: With "new Delete().from(Car.class);" I don't get an error - but nothing isn't deleted.

Hi, so I have just integrated Ollie in my newest app and it is giving me strange errors. It compiles without any errors, but crashes right on startup.

Here's the stacktrace: https://gist.github.com/anonymous/a8d3fcb2fb4cd92a2dc4

I believe I've added it using Gradle the right away:

compile 'com.michaelpardo:ollie:0.3.1'
provided 'com.michaelpardo:ollie-compiler:0.3.1'

Here's the model:

@Table(SavedDefinitions.TABLE_NAME)
public class SavedDefinitionEntry extends Model {

    // Data
    @Column(SavedDefinitions.KEY_WORD)              public String mWord;
    @Column(SavedDefinitions.KEY_PHONETIC_TEXT)     public String mPhoneticText;

    public SavedDefinitionEntry(String mWord, String mPhoneticText) {
        this.mWord = mWord;
        this.mPhoneticText = mPhoneticText;
    }

}

I am having a hard time solving this error. Any ideas? :(

when I define a model, and then run the app, it has errors. Error:Execution failed for task ':app:compileDebugJava'.

java.lang.NoClassDefFoundError: android/content/ContentValues

i Use api 21.

I have an integer column with null-values inside. I store dates in this col. If I load the ollie-object I always get dates with 0 -> 01.01.1970 How can I get the null value (stored in the database) back?

If I load the value from db with fetchValue(String.class) I get the null value...

First off, I'm totally looking forward to continuing to play around with ollie. I stumbled across this issue while testing our ollie in my application. I had a entity lets call it "notebook" which contained a "note". I could successfully create the notebook and see it in my notebook list view and the database looked correct. But once I killed the app and reopened it I would get NPE in my notebook list view because the note was null (even though an tag id was successfully populated in the database)

I traced it back to the ModelAdapter which was attempting to load the Note using the field on the entity. The note field on the entity was null because the entity was being loaded fresh from the database.

Here is the generated source file:

public final class Notebook$$ModelAdapter extends ModelAdapter<Notebook> {
            public final Class<? extends Model> getModelType() {
                return Notebook.class;
            }

            public final String getTableName() {
                return "notebooks";
            }

            public final String getSchema() {
                return "CREATE TABLE IF NOT EXISTS notebooks (_id INTEGER PRIMARY KEY AUTOINCREMENT, name TEXT, note INTEGER)";
            }

            public final void load(Notebook entity, Cursor cursor) {
                entity.id = cursor.getLong(cursor.getColumnIndex("_id"));
                entity.name = cursor.getString(cursor.getColumnIndex("name"));
                entity.note = Ollie.getOrFindEntity(entity.note.getClass(), cursor.getLong(cursor.getColumnIndex("note")));  // This is the NPE
            }

            public final Long save(Notebook entity, SQLiteDatabase db) {
                ContentValues values = new ContentValues();
                values.put("_id", entity.id);
                values.put("name", entity.name);
                values.put("note", entity.note != null ? entity.note.id : null);
                return insertOrUpdate(entity, db, values);
            }

            public final void delete(Notebook entity, SQLiteDatabase db) {
                db.delete("notebooks", "_id=?", new String[]{entity.id.toString()});
            }
}

I want to make sure that this assertion is what people expect when an entity is deleted:

Note note = new Note();
note.body = "this is draft";
note.save();
Delete.from(Note.class).execute();

assertThat(note.id).isNull();

There are several operations we might expect (or not) when an entity is deleted. These operations could be supported by overloading Delete.execute() with booleans.

• Set entity id to null.
• Set entity to null.
• Remove entity from cache.

I think it's reasonable to set id to null because it no long exists in the database, however I can think of scenarios where there is use for it.

I don't think it's reasonable (as a default) to set the entity to null. If there are entities used elsewhere in the app, they will then be null.

Removing entities from the cache seems reasonable, since there is no scenario where they will be retrieved from it. However, it won't hurt to leave them in there since they will be evicted naturally from lack of use (LRU cache). The only issue with this is that the cache will eventually grow to its max size.

My preference is to only set id to null and provide an override of Delete.execute() whereby passing in false will not set the id to null.

Thoughts?

Hello. Before anything else, thanks for creating Ollie. Now, I cannot understand why, but I'm unable to build my project with this library. The only error I'm seeing is:

Error:Execution failed for task ':SMSX:compileDebugJava'.
> java.lang.NullPointerException

That's it. Nothing else. Model class: https://gist.github.com/anonymous/3c3cb0465b8ecdd2ee57

I'm initializing Ollie inside my Application class. Any idea how to fix this? Thank you.

Update: So replacing the primitives in my model class with their Wrapper classes fixed the issue. Am I doing this right?

I opened up https://github.com/pardom/ollie/issues/18. I have created a fix for the issue and created some unit tests. I'm not sure if this is the expected behavior, but it seems to be working for me. Hopefully, it helps.

if I have an entity with id value, when I call save, it could not be inserted into the database. can you provide model.replace() method?

when the contentprovider is supported, everytime I save the entity, it will call notifychange(), sometimes, I want to insert a list of entities into the database, it will call notifychange() many times, can you provide some funtion to prevent notifychange().

I'm getting a NPE and I don't know why. :-(

:app:compileDebugJava FAILED

Caused by: java.lang.NullPointerException at ollie.internal.codegen.Registry.getTypeAdapterElement(Registry.java:83) at ollie.internal.codegen.element.ColumnElement.(ColumnElement.java:73) at ollie.internal.codegen.step.ModelAdapterStep.addColumnElements(ModelAdapterStep.java:89) at ollie.internal.codegen.step.ModelAdapterStep.process(ModelAdapterStep.java:65)
at ollie.internal.codegen.OllieProcessor.process(OllieProcessor.java:76) at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:793) at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:722) at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1700(JavacProcessingEnvironment.java:97) at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1029) at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1163) at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1108) at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:824) at com.sun.tools.javac.main.Main.compile(Main.java:439) ... 65 more

BUILD FAILED

Great work on this library. I was always a fan of the syntax in https://github.com/pardom/ActiveAndroid, but the performance hit against reflection on annotations seemed like a downside so I was really happy to see Ollie pop up.

One of the things I didn't particularly like when integrating with my existing model schema was that all the fields had to be public, so I added a new annotation called @GetSet that tells the generated classes to look for getter and setter methods instead of accessing the fields directly.

Hello community,

Ollie is now deprecated. I'm grateful for everyone's contributions and support over the years, however I believe that there are many better alternatives. Ollie was an attempt to make a better ActiveAndroid alternative, and that library is also deprecated as of today.

The reason this notice is coming to you via GitHub issue rather than the README is because I no longer have access to this GitHub account. Now that this account has been dormant for six months, I have reclaimed my username, but still do not have contributor access. I don't know how long the dormant account will remain visible, so I suggest forking the library if you wish to continue work on it.

I strongly endorse Square's excellent SQLDelight as an alternative to this library.

Thanks again,

Michael Pardo

apply plugin: 'com.android.application'

android { compileSdkVersion 23 buildToolsVersion "23.0.2" defaultConfig { applicationId "com.leavingstone.aversi" minSdkVersion 16 targetSdkVersion 23 versionCode 1 versionName "1.0" }

dataBinding {
    enabled = true
}

buildTypes {
    release {
        minifyEnabled false
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    }
}
lintOptions {
    disable 'InvalidPackage'
}

} dependencies { compile fileTree(dir: 'libs', include: ['*.jar']) compile files('libs/core-3.2.1-sources.jar') compile files('libs/core-3.2.1.jar') testCompile 'junit:junit:4.12' compile 'com.android.support:appcompat-v7:23.2.0' compile 'com.android.support:design:23.2.0' compile 'com.specyci:residemenu:1.6+' compile 'eu.the4thfloor.volley:com.android.volley:2015.05.28' compile 'com.google.code.gson:gson:2.5' compile 'com.android.support:percent:23.2.0' compile 'com.jakewharton:butterknife:7.0.1' compile 'com.google.android.gms:play-services:8.4.0' compile 'com.michaelpardo:ollie:0.3.1' provided 'com.michaelpardo:ollie-compiler:0.3.1'

} apply plugin: 'com.google.gms.google-services'

I'm seeing some strange behavior. I added a field to a class and incremented the DB version number so I should have the new column but I'm seeing:

E/Ollie﹕ Failed to process cursor.
    java.lang.IllegalStateException: Couldn't read row 0, col -1 from CursorWindow.  Make sure the Cursor is initialized correctly before accessing data from it.

And a no such column SQLLite exception:

E/LoginFragment﹕ Encountered a problem with login.
    android.database.sqlite.SQLiteException: no such column: profile_image_id (code 1): , while compiling: UPDATE users SET apid=?,profile_image_id=?,password=?,external_id=?,last_name=?,email=?,authentication_token=?,_id=?,first_name=?,phone_number=? WHERE _id=?

Any suggestions appreciated.

Hello, it seems that there are concurrency issues. I have an ollie model Task.java with 2 tables:

    @SerializedName(SERVER_ID)
    @Column(SERVER_ID)
    @Unique(ConflictClause.REPLACE)
    public String mServerId;

    @Column(NEW_CONTENT)
    public Boolean mHasNewContent;

    public synchronized void setServerId(String serverId) {
        mServerId = serverId;
        save();
    }

    public synchronized void setHasNewContent(Boolean accessed) {
        mHasNewContent = accessed;
        save();
    }

If Thread A calls setServerId and Thread B calls setHasNewContent right after that, it can happen, that the mServerId is lost and back to null.

Any ideas why and how this can happen? I don't seem to can synchronize this case outside of Ollie by myself.