Added functionality for non-autoincremented id fields. #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added support for id fields that don't need autoincrement functionality that were otherwise impossible to be modelled. To achieve this goal an additional base class was introduced that doesn't have an id field preset (in this update
BaseEntity
is the base class for all entities that must control its id generation manually andBaseAutoIdEntity
is the base class for the entities with autogenerated ids).Right now there is a possiblility to map the following two entities (e.g. country lookup table with char code primary key and standard auto-id entity):
and
BaseEntityService
can now be used with both entities:and
It also leaves an opportunity to have a base class with id field that must support anything different from
GenerationType.IDENTITY
, e.g.GenerationType.SEQUENCE
, as it could otherwise only be modified on a per-mapped superclass basis via xml and thus have impact on all implementing classes.