When to use execute_batch?

[zjp-CN]

execute finishes one sql query at a time. So will execute_batch be more efficient if multiple sql queries are required?

But after I glance at the source code, I find execute_batch actually break down queries and process one at a time.

rusqlite/src/lib.rs

Lines 510 to 521 in a37489e

	while !sql.is_empty() {
	let stmt = self.prepare(sql)?;
	if !stmt.stmt.is_null() && stmt.step()? && cfg!(feature = "extra_check") {
	// Some PRAGMA may return rows
	return Err(Error::ExecuteReturnedResults);
	}
	let tail = stmt.stmt.tail();
	if tail == 0 || tail >= sql.len() {
	break;
	}
	sql = &sql[tail..];
	}

My question is whether sqlite receives multiple requries that are passed to execute_batch?

[gwenn]

execute_batch is like sqlite3_exec but without callback.
SQLite doc says:

The sqlite3_exec() interface is a convenience wrapper around sqlite3_prepare_v2(), sqlite3_step(), and sqlite3_finalize(), that allows an application to run multiple statements of SQL without having to use a lot of C code.

So this doesn't mean more efficient, just more convenient.
And both execute_batch and sqlite3_exec prepare and execute multiple queries.