[BUG] - @Default with @LogicalDeleted updated field only default value enumeration

[valback3]

Jimmer Version

0.10.6

JDK Version

JDK 25

Database

PostgreSQL

OS

Windows

Expected behavior

I expect that the value I am writing (different from @LogicalDeleted) will update the value stored in the database

Actual behavior

But the generated SQL query immediately includes a query with the default value.

Description

When using an enum as a flag for @LogicalDeleted, the value specified by @default is always set during an update. However, the documentation states that @default does not affect update operations, only insert operations.

Reproduction steps

To reproduce the bug, you need to save an entity with a status (enumeration) @default, and then update the status column to a value different from @LogicalDeleted.

Generated SQL

No response

Relation Model

Screenshots

No response

Logs

No response

[LanXa7]

Setting that aside for now, the status field shouldn’t be a logically deleted field in the first place, should it? I took a look at the documentation for the @default annotation, which states that “does not affect updates” refers to updates to the entity itself, not to this field specifically. This is because, in the author’s design, this field was likely never intended to be updated manually.

[LanXa7]

debug I took a look at the source code, and that's how it's designed, so you should avoid using it this way. From the author's perspective, this issue isn't a bug. If you're interested, you can check out the source code yourself.

[DokKevlar]

I checked it out.
And I agree that for boolean, int it is justified.
However, it may be worth changing the logic for ENUM or VARCHAR, otherwise the very meaning of using these data types.