Was the Oracle sequence bug seen in here:
fixed in a subsequent version?
We are running v4.3.8 and see the bug. We can either alter our code (expensive and time-consuming) or upgrade our version of Hibernate (presumably less expensive and time-consuming).
Thanks,
-t