Running on b39 with XP ...
After a few deploy/undeploy with drop/create the generator table is getting very
dirty with multiple rows holding the same "SEQ_NAME" (pkColumnName) +
IMHO, if a tuple x(SEQ_NAME,SEQ_COUNT) is already existing do we need to
recreate it ?
This is also a problem with the face the spec talks on Â§9.1.36 of "primary key"
and that the generated table in Derby is not using any PK at all !
table generator needs to be revised with real PK and trying to keep this table
clean whatever is the runtime scenario ...
TableGenerator is a key feature for legal identifiers that makes mandatory the
id to sequential and continuous (for instance invoice numbers).