FOREIGN KEY constraint failed (code 787)

Hi, I have the following schema on DB Flow.

`

@ModelContainer
@Table(database = BookingDatabase.class)
public class ComposedBooking extends BaseModel 
  public List<RoomModel> roomModels = new ArrayList<>();

@OneToMany(methods = {OneToMany.Method.ALL}, variableName = "roomModels")
    public List<RoomModel> getRoomModels() {
        if (roomModels == null) {
            roomModels = new SQLite().select()
                    .from(RoomModel.class)
                    .where((RoomModel_Table.room_booking_id).eq(id))
                    .queryList();
        }

        return roomModels;
  }

@ModelContainer
@Table(database = BookingDatabase.class)
public class RoomModel extends BaseModel

@Column
    @ForeignKey(references = {@ForeignKeyReference(columnName = "room_booking_id", columnType = Long.class, foreignKeyColumnName = "id")}, saveForeignKeyModel = false, onDelete = ForeignKeyAction.CASCADE, onUpdate = ForeignKeyAction.CASCADE)
    public ForeignKeyContainer<ComposedBooking> composedBookingRef;


    public void setRoomModelComposedBookingKey(ComposedBooking composedBooking) {
        if(composedBooking == null){
            Timber.e("Composed booking is null");
            return;
        }
        Timber.v("Composed booking not set");
        composedBookingRef = FlowManager.getContainerAdapter(ComposedBooking.class).toForeignKeyContainer(composedBooking);
    }
`

However, when I associate the table RoomModel with the ComposedBooking class.

When I call roomModel.setRoomModelComposedBookingKey(composedBooking); roomModel.save(); . It throws the error FOREIGN KEY constraint failed (code 787) android.database.sqlite.SQLiteConstraintException: FOREIGN KEY constraint failed (code 787)

However if call save() before associating the foreign key , it works. Why am I not able to save after associating the foreign key?

I am using 'def dbflow_version = "3.0.0-beta2"' as default.

Please help. Thanks!

[agrosner]

Hope that makes sense. SQLite works that way - you can save a NULL or an existing Foreign Key on an object with that reference. But it must exist first. and you cannot delete the parent until children are taken care of.

[agrosner]

Are you saving the ForeignKeyContainer associated Model object before associating it and saving it to the DB? So what was fixed in beta-3 is that we now save the associated foreign key object before saving the child to the DB, but thats only if you forgo the ForeignKeyContainer object structure. you still need to save the parent object before saving the child RoomModel. What you can do is override the save() method and save the associated Model. You cannot save ForeignKeyContainer objects directly.