Yeah, the whole PK generation abstraction is somewhat leaky. It works, but is
challenging to apply consistently across different DB engines and different
generator strategies. And as a result is challenging to present to the end user
in a sane fashion. Just recently had this discussion with Niki
When using the modeler, you can choose to pick Custom Sequence as a choice
for the primary key generation. Provide the sequence name, and then
there's this field in the modeler, "Cached PK Size". It wasn't obvious to
me, and it took a bit of sleuthing to find that this value should be the
increme
