[bug] Delete statement by foreign_key column generates additional select about jimmer HOT 4 CLOSED

The problem is coming from MutableDeleteImpl line 122.

Expression

boolean directly = table.isEmpty() && binLogOnly && (
        isDissociationDisabled ||
        sqlClient.getEntityManager().getDissociationInfo(table.getImmutableType()) == null
);

is erroneously evaluated to false, because table.isEmpty() = false.

But I believe directly should be equal to true because query can be executed directly.
To make decision we need to analyze AST and used properties.

from jimmer.

This is not a bug, because there is many-to-many association Book.authors, Jimmer must check whether there are some records of BOOK_AUTHOR_MAPPING need to be deleted.

Of course, you can apply on delete cascade to BOOK_ID of BOOK_AUTHOR_MAPPING to let database handle this issue.

If on delete cascade is used, the current solution(Smarter solution will be supported in future) is disableDissociation

sql
    .createDelete(Book::class) {
        where(table.storeId eq 1)
    }
    .disableDissociation() // Here is the configuration, think nothing and directly delete rows
    .execute()

from jimmer.

In next version, you have another choice:

@JoinTable(cascadeDeleteBySource = true)
List<Author> authors();

from jimmer.

Try 0.8.113

from jimmer.