Why Does My Go Program Get a 'Database is Locked' Error in SQLite3 Even with Only One Connection?

Understanding the "Database is Locked" Error in Go with Sqlite3

When working with SQLite3 database in Go, encountering the "database is locked" error can be a puzzling experience. This error typically arises when multiple threads attempt to access the same database file concurrently. However, it's worth noting that you mentioned getting only one connection in your program.

Upon investigating the issue further, you correctly identified that despite closing all query results, multiple handles of the database file were created. This can be confirmed using the Opendfileview program. To resolve this issue, let's analyze the provided code and identify where the problem may lie.

The getDatabaseHandle function initializes a connection to the SQLite3 database and starts a transaction. It returns the created database handle and a pointer to the transaction. Within the dosomething function, you execute a query on the database, then close the result rows. Afterward, you perform some insert queries within the transaction, ultimately committing it.

Examining the code, you may notice that the rows.Close() call is not deferred. This could leave the result rows open and result in additional database handles. Try deferring the row closure as shown below:

if err != nil {
    return err
}
defer rows.Close()
if rows.Next() {
    ...
}

By deferring the row closure, you ensure that the result rows are closed even if an error occurs. This will help release any associated database handles and prevent the "database is locked" error.

The above is the detailed content of Why Does My Go Program Get a 'Database is Locked' Error in SQLite3 Even with Only One Connection?. For more information, please follow other related articles on the PHP Chinese website!