Releases: babyfish-ct/jimmer
v0.7.47
Fix issue#72, #73 and #75
v0.7.45
v0.7.44
Support Oracle
v0.7.43
Support jimmer.offset-optimizing-threshold
v0.7.39
v0.7.37
Important version
- Supports remote association across different micro-services
- Supports
@ManyToManyView
v0.7.22
Fix #53
v0.7.19
Fix bug caused by new feature @IdView
v0.7.14
-
Save command upgrade
-
For root objects, key is optional. If there is no id and key, it means non-idempotent forced insertion
-
for associated objects
- key is optional if
setAppendOnly/setAppendOnlyAll
is configured. If there is no id and key, it means non-idempotent forced insertion; - Otherwise, as before, since there is no id and no key will result in an error
- key is optional if
-
-
Filter Validation Rules
If an entity type is affected by a global filter (including built-in filters like @LogicalDeleted), all many-to-one and one-to-one relationships that refer to it must be nullabe, otherwise an error will be reported
-
Fake foreign key
@joincolumn supports the
foreignKey
attribute, which is true by default, indicating that this is a real foreign key; users can set it to false, indicating a fake foreign key (in the developer's brain, this is an foreign key; but it is not in real database. For table sharding and microservices) -
Database vadliation
The SpringBoot configuration file supports the configuration attribute
jimmer.database-validation-mode
, which defaults to NONE and can be set to WARNING and ERROROnce set, the database structure and entity declarations are checked for consistency at startup.
- No matter how many errors there are, it will be reported in one go in a list
- Validation currently implemented: table name column name, nullability, primary key, real foreign key.
- If some entity classes or attributes do not want to be added to the verification temporarily: use @DatabaseValidationIgnore to decorate