phase out IdGeneratorStrategyInterpreter

[gavinking]

I would like to propose that we essentially drop IdGeneratorStrategyInterpreter and the current logic for instantiating an id generator for a JPA @GeneratedValue, and:

• just plain hardwire-in the interpretation of the GenerationTypes in terms of our build-in Generators, and
• start instantiating them via constructors which accept annotations, as we do with our new stuff.

(A motivating factor here is to migrate to the use of UuidGenerator, which is currently impossible.)

Of course we would need to keep a map of named id generator -> defining annotation instance (a TableGenerator, SequenceGenerator, or GenericGenerator annotation).

This might be a more-radical proposal than it needs to be, so perhaps @sebersole can come up with a "compromise"?

[gavinking]

Of course we would need to keep a map of named id generator -> defining annotation instance

Excuse me, that's not quite right. We would have a map of name to id generator instance. We would instantiate the generator when we encountered the TableGenerator, SequenceGenerator, or GenericGenerator annotation.

[sebersole]

https://hibernate.atlassian.net/browse/HHH-14496

[gavinking]

OK, great.

[sebersole]

We should close this one imo to avoid split discussion

[gavinking]

OK sure