SQL for Java Devs · interview question

In the context of JDBC batch processing, what is the effect of using setAutoCommit(false) and manually committing the transaction after executeBatch()?

Multiple choiceHardchapter-8-curatedpremiumsql-for-java-devsbatching

java

conn.setAutoCommit(false);
PreparedStatement ps = conn.prepareStatement(sql);
ps.addBatch();
// more batches
ps.executeBatch();
conn.commit();

Prevents any statement from executing until they are all committed.Ensures atomicity across all batched statements.Decreases performance due to additional transaction overhead.Increases the chance of deadlocks in the database.

Answer and explanation

Correct answer

B. Ensures atomicity across all batched statements.

Why

Using setAutoCommit(false) and manually committing after executeBatch() ensures that either all statements in the batch are committed together, achieving atomicity, or none are if an error occurs.

Test yourself on SQL for Java Devs

A free test with instant, explained results. No account needed.

Start free test

All SQL for Java Devs questions →

In the context of JDBC batch processing, what is the effect of using setAutoCommit(false) and manually committing the transaction after executeBatch()?

Correct answer

Why

More SQL for Java Devs questions