Add onConflict() method to @PrimaryKey annotation

DBFlow Version: 3.0.1 Issue Kind (Bug, Question, Feature): Feature

Description:

DBFlow does not support adding ON CONFLICT clause to @PrimaryKey annotation. Trying to add @Unique(onUniqueConflict = ConflictAction.REPLACE) to our primary key column does not seem to work. For example:

@Table(database = AppDatabase.class, name = "tbl_persona", allFields = true)
public class Persona extends BaseModel {

    @PrimaryKey
    @Unique(onUniqueConflict = ConflictAction.REPLACE)
    @Column(name = "id_persona")
    int idPersona;

    @NotNull
    String nombre;

    // ...
}

results in the following creation SQL query:

CREATE TABLE `tbl_persona`(`id_persona` INTEGER UNIQUE ON CONFLICT REPLACE,`nombre` TEXT NOT NULL, PRIMARY KEY(`id_persona`))

wich is not as expected.

According to SQLite documentation and own testing, the correct creation SQL query for the ON CONFLICT clause in primary key should be like this:

CREATE TABLE `tbl_persona`(`id_persona` INTEGER PRIMARY KEY ON CONFLICT REPLACE,`nombre` TEXT NOT NULL)

or like this:

CREATE TABLE `tbl_persona`(`id_persona` INTEGER,`nombre` TEXT NOT NULL, PRIMARY KEY(`id_persona`) ON CONFLICT REPLACE)

Any suggestion is welcome 😃

[dleonett]

@agrosner I made it work for me by using insertConflict = ConflictAction.REPLACE in @Table annotation, and removing the @Unique annotation from my primary key column. It looks like this:

@Table(database = AppDatabase.class, name = "tbl_persona", allFields = true, insertConflict = ConflictAction.REPLACE)
public class Persona extends BaseModel {

    @PrimaryKey
    @Column(name = "id_persona")
    int idPersona;

    @NotNull
    String nombre;

    // ...
}

[luorenyu]

@agrosner I encounter the same issue.but My DBFlow version is 4.0.0-beta5. and I try to add this annotation @Table(primaryKeyConflict = ConflictAction.REPLACE),but it doesn’t work .but @dleonett 's solution did work!