I have been trying my hardest to ignore that we have both GenerationTime and, in another package, GenerationTiming, the two enums being isomorphic and differing only by an ing. But today I noticed that GenerationTime isn’t even used consistently in its own package. @CurrenTimestamp is defined in terms of GenerationTiming. So this is super-confusing, and it’s time we deprecate one of them. The obvious candidate is GenerationTime, since GenerationTiming us used by all the value generation stuff. On the other hand, GenerationTiming is in the org.hibernate.tuple package, my least-favorite package, so it’s not quite perfect either. Anyway one of them has to go. |