Mechanism to override the ID generation defined into the mapped superclass

[nexus061]

Good morning everyone, In cases where we have mapped superclasses that contain the ID generation declaration, it's currently not possible to override the behavior if the annotations are placed at the field level. I suggest we make it so that if the field is overridden in the child entity, it's also possible to change the behavior. Imagine this scenario: I have an auto-generated field with a sequence, but due to a requirement, I need to import data from an old system while maintaining the old progressive numbering. I was forced to modify my hierarchy to be able to do this. What do you think?