Little question to the community:
Does it make sense to have a single hi_value table containing a record with the next high value per id sequence ?

Currently, if you want distinct id sequences per persistent entity when using the TableHiloGenerator, you have to create one table per persistent entity.

Maybe this strategy could be upgraded to support a single table with several records in it...

Does it make sense or does it open the door to any potential problem or performance penality ?

I've considered that. But you can always implement it yourself... Many applications define their own IdentifierGenerator.

Was looking at it...

But I faced a problem for which I don't have any solution.

The TableGenerator is a PersistentIdentifierGenerator. As such it returns the SQL create statement for the persistent table.

If the same table is shared by different generators, the create statement will be different (the frist will be an actual create while the others will just add the initial value).

Unfortunately, the SessionImplementor is not available within the sqlCreateStrings() - so there is no way to know if the table already exists (besides using 'if exist' statement in the sql itself - but this is not supported by all databases).

Any idea ?