Hi,
We are considering to replace our existing DB2 with Maria DB . We current use Sequence objects in DB2 for primary key generation. One of the tings I came across was that if using an identity generator instead of a sequence generator (since user defined sequence objects dont seem to be supported in Maria DB as its similar to MySQL) , jdbc batch inserts will be implicitly disabled if using an identity generator. More info below in an older thread related to that (though it is related to MySQL),

viewtopic.php?p=2436697


Using the Table generation strategy seems to be one option, but it has its own pros and cons when coming from a Sequence generation strategy which we currently have.
Any suggestions for other options related to above will be helpful.

regards
aravias

You will not be able to use JDBC batching for insert statements only. Updates and deletes are batchable on MySQL and MariaDB even when using the IDENTITY generator.

I run some tests to compare if it's worth to use the table generator and take advantage of insert batching, but the truth is that it's still slower than IDENTITY. The table generator uses row-level locking, and even if you use the pooled optimizer, the row-level locking and the fact that you require a separate transaction will impact performance, especially when increasing concurrency.

All in all, use IDENTITY even if the inserts are not batched.

okay thanks.