Databases
StackOverflow2013
Postsdbo
POSQLite keeps the database locked even after the connection is closed
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSQLite keeps the database locked even after the connection is closed
    primarykey
    data
    text
    <p>I'm using System.Data.SQLite provider in an ASP.NET application (framework 4.0). The issue I'm running into is that when I INSERT something in a table in the SQLite database, the database gets locked and the lock isn't being released even after the connection is disposed. </p> <p>When trying to access the file, the error is: "The process cannot access the file 'catalog.sqlite' because it is being used by another process."</p> <p>My code is pretty straightforward, I open the connection, read some data from a SQLServer database, insert that data into SQLite (through SQLiteDataAdapter) and then close the connection and dispose everything just to be on the safe side. But still, I get that error when I try to zip the file after it's being populated with the data.</p> <p>I've read all kind of suggestions here on StackOverflow but none of them has helped solving the problem (turning off the antivirus, changing the transaction model, waiting a few seconds before zipping up the file, wrapping all the insert calls into a transaction, etc.. but none has helped solving this issue.</p> <p>Maybe there's something specific to ASP.NET (multithreading being the issue? Even though I'm testing it on a development machine where there's only one call to that function and no concurrency?)</p> <p>As a side note, I tried avoiding DataTable and SQLiteDataAdapter and using only SQLiteCommand directly and that way it works a charm. Of course I can keep building my queries as strings instead of using the data adapters, but I kind of find it a bit awkward when there's a framework built to do that.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USValerio Santinelli
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSQLite keeps the database locked even after the connection is closed
      1. USedymtt
      1. VTFavorite
    2. VO
      singulars
      1. POSQLite keeps the database locked even after the connection is closed
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSQLite keeps the database locked even after the connection is closed
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAre you wrapping the commands and connections in using statements?
      singulars
      1. POSQLite keeps the database locked even after the connection is closed
      1. USArran
    2. COIs this lock by your application, i.e., does the lock vanish when it exits?
      singulars
      1. POSQLite keeps the database locked even after the connection is closed
      1. USCL.
    3. CO@Arran I'm not wrapping the connection with using. But I'm not wrapping it even with the version that works without locking (aka the one using commands instead of data adapters).
      singulars
      1. POSQLite keeps the database locked even after the connection is closed
      1. USValerio Santinelli
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload