Your post is clear and precise.

We know Oracle is transaction oriented by default and if you issue INSERT statements like with AUTOCOMMIT set to false:

INSERT INTO tbl_name(tbl_id, tbl_col_name)
VALUES(sequence_name.nextval, ‘Name’);

…and then you don’t COMMIT, the tbl_id column would have “gaps” in the next COMMIT.

I wonder what happens when you work with a transaction capable DB engine in MySQL and the AUTOINCREMENT function.

What if you generate INSERTs and then ROLLBACK without COMMITting in MySQL + InnoDB? Does the engine generate “gaps” if in the meantime another user COMMITs records…?