Use UPDATE event type for generator where applicable

[marko-bekhta]

fixes #2138

I've added the test as disabled, as we'd need an ORM release that fixes https://hibernate.atlassian.net/browse/HHH-19306 first

[DavideD]

Thanks for the PR, but does it make sense to merge this without the fix for ORM?
I don't see any benefit, I think I would prefer to have the test enabled and then apply this fix after the next ORM release.

[marko-bekhta]

yeah... that would be best to wait for the ORM fix and then apply this patch... I did want to run the CI build against all DBs (was only testing postgres locally) to make sure it doesn't break something else 😃

[DavideD]

Make sense, but the fix looks simple enough that I don't expect problems with the other databases (finger crossed).
And even if it does, it shouldn't be too hard to fix (or we can fix it as a separate issue).

You've already done the hard part 😃
(figuring out the issue and propose a solution)

I'm more worried about merging this and forgetting to reenable the test.

[DavideD]

@marko-bekhta Now that https://hibernate.atlassian.net/browse/HHH-19306 has been merged, you can rebase this PR on top of wip/3.0 and it will test correctly as soon as the ORM snapshot has been released.

[marko-bekhta]

👍🏻 rebased and changed the patch for wip/3.0.
I'm thinking since we have that fix for 6.6 too (hibernate/hibernate-orm#9946), maybe we want to backport to 2.4 so we could bump it in Quarkus?

[DavideD]

I will backport it, thanks

[DavideD]

@marko-bekhta Could you rebase this on top of main, please? We can merge it now

[marko-bekhta]

changing the base branch in PR makes GH do strange things 😄, but looks like tests are running now 🤞🏻

[DavideD]

Thanks @marko-bekhta, perfect!