OpenJPA's implementation (TableJDBCSeq) of the table based sequence generation stores the sequence state in a table called OPENJPA_SEQUENCE_TABLE. There can be one counter over all entities or a separate counter per entity class.
How are you experiences with many JPA applications (n >> 1) using the table strategy with a single shared DB2 schema? Won't there be locks on the OPENJPA_SEQUENCE_TABLE when multiple applications select their new sequence values? If using a separate counter per entity class, will there be at least only locks per row (and not per table)? TIA, Tobias -- View this message in context: http://openjpa.208410.n2.nabble.com/Experiences-with-GenerationType-TABLE-based-sequences-tp5818894p5818894.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
