insertOrUpdate method in DAOs about greendao HOT 3 OPEN

will insertOrReplace() work based on unique indexes rather than primary key

@Entity(
        indexes = {
                @Index(value = "uniqueId", unique = true)
        }
)
public class Model  {
    @Id (autoincrement = true)
    private Long id = null;
    
  private String uniqueId = null;
}

This is my Entity Class . Now can i do insertOrReplace based on uniqueId rather than primary key Id.

from greendao.

Will be nice to get an option, annotation or anything to prevent clearing records by null values. In my case I'm downloading list of magazines without any details:

[
    {
        "id" : 1,
        "title" : "test 1"
    },
    ...
]

But for some magazines I save more details about them:

{
    "id" : 1,
    "name" : "test 1",
    "description" : "Lorem ipsum"
}

And now is problem with keeping magazine details (description in this case) during update of magazine list.

from greendao.

When using a join table to build an N:M relationship, insertOrUpdate would be very useful. I have Folder, Envelope, and EnvelopeFolderJoin tables. Both Envelope and Folder have unique GUID indexes, as well as the "id" PK columns. When I insert a new Folder, I also insert the Envelopes and associated EnvelopeFolderJoin rows. However, if that folder references envelopes that already exist, those envelope rows are deleted and recreated, breaking any existing links other folders.

from greendao.