Depending on your database capabilities, the native ID generation strategy will use:
- the IdentityGenerator where supported (eg. SQL Server);
- the SequenceGenerator where supported (eg. Oracle);
- otherwise the TableHiloGenerator.

We are required to support both SQL Server (development) and Oracle (production) databases - so the native strategy might be a good choice.

Unfortunately, this strategy is not very efficient since the Identity/Sequence-Generator require at least 2 SQL queries by Insert (and we have lots of inserts).

We are wondering if an additional nativehilo strategy could be defined. It would behave as follows:
- use the SeqHiloGenerator where supported (eg. Oracle);
- otherwise the TableHiloGenerator.

Does it make sense ?

(I'm actually wondering if the SeqHiloGenerator will give any additional benefit compared to the TableHilo - we could use the latest in all cases anyway).

I've implemented such Generator.
Tell me if someone is intrested and I'll make it available to others.

Rem:
Wasn't obvious to me when reading the doc, but you can specify a custom generator class - the class attribute in the generator mapping is not restricted to those provided by default - it can be a full class name.

Post it into the wiki area. please.