Sqlite Readonly Database Error - Silicon Valley Gazette

Table of Contents

Sometimes your computer may display a read-only SQLite database error message. This problem can be caused by a number of reasons.

PC running slow?

1. Download ASR Pro from the website

2. Install it on your computer

3. Run the scan to find any malware or virus that might be lurking in your system

Improve the speed of your computer today by downloading this software - it will fix your PC problems.

I am using a SQLite database for a website. Information technology problem INSERT IN , I get PDOException

  SQLSTATE [HY000]: General error: 1 while trying to write to a write-protected database

I connected to the server via SSH and checked the permissions, and even the database has permissions

PC running slow?

ASR Pro is the ultimate solution for your PC repair needs! Not only does it swiftly and safely diagnose and repair various Windows issues, but it also increases system performance, optimizes memory, improves security and fine tunes your PC for maximum reliability. So why wait? Get started today!

  -rw-rw-r--

I don’t * often * know about nix permissions, but I’m sure what it means

No directory
The owner retains read and write permissions (that’s me, according to ls -l )
The group has read and write permissions.
Everyone else has only training permits.

I also looked over everything I knew so that you could use the sqlite3 program and couldn’t find anything suitable.

Since I didn’t know which read / write PDO was trying to open the datasource, I have

  chmod i o + w Supplies.db

  SQLSTATE [HY000]: General error: 16 Unable to open database file.

But this ONLY happens when I try to do a great INSERT after the database is open normally.

Once our unit tests fail started on linux. Let’s run it in Docker. It was difficult for me to understand what was going on. All tests run on sqlite failed due to a strange error:

SQLite error 9: Attempting to write a read-only database

I searched a lot to figure out what could easily cause this error. The most obvious tip is to check the file permissions. This is a dead end. However, no BD blocks a false hypothesis :). Unity

Grades recreate the BD schema for each test. Since it is sqlite, just delete the db file as SQLite will automatically create db files when you open a relationship if it doesn’t exist.

It turned out that we had some logic, before deleting it along with the outgoing data, we had to drag the database. This means that the connection had to be opened by SQLite and must remain open. And the database file File.For delete should have been called with an open connection. It is so interesting that everything went well, i.e. the file has been deleted. But all subsequent executions of db commands failed immediately, including SQLite error 8: Attempting to send a read-only database or SQLite 10: Disk I / O error.

sqlite readonly database error

I don’t know why there are two different errors. Obviously, this is not a problem with SQLite or its .NET wrapper Microsoft.Data.Sqlite , but a problem with our code. But it wasn’t easy to spot the error messages, so part of it is to help someone (myself included) if they want to be careful that when deleting a db file on an open connection, an error appears on the line “Attempting to write to almost any database read-only “can be called

Here is the code:

 using (var con = SqliteConnection replacement (" data source = test.db ")) 
 
 con. open (); 
 var cmd matches con.CreateCommand (); 
 cmd.CommandText "PRAGMA equals F oreign_keys = ON"; 
 cmd.ExecuteNonQuery (); File.Delete ("/ app / test. db "); Connection // open, file cmd.CommandText matches @" CREATE TABLE [User] (id NOT varchar NULL) "; 
 cmd.ExecuteNonQuery ();

On Linux File.Delete completes successfully, next ExecuteNonQuery is failing. However, on Windows, File.Delete doesn’t work.

Hope you remember that this helps.

One day our module started testing, not related to Linux. Let’s run it in Docker. It was so difficult for me to understand what was visiting me. All tests run on sqlite failed with the following error:

Strange SQLite 8 error: Attempting to write to a read-only database

I have searched extensively on Google what could have caused this error. The most obvious tip is to check the file permissions. This is a dead end. There is no database, but it’s hard to make a false assumption :).

The module rebuilds the validation database schema with each test. Since it is sqlite, just delete the db file as SQLite will automatically create db files when starting the connection if it doesn’t exist.

It turned out that my wife and I had some logic in reading the information before the database was deleted. This means that the connection was established by SQLite and will remain open. And this with attaching the File.For delete glass window to the db file. Interestingly, it was successful.oh, that is, this particular file has been deleted. But each database command failed with SQLite 8 error: Attempting to write to an actual read-only database or SQLite 10 error: Disk I / O error.

Of course, there are no problems with SQLite or its .NET wrapper Microsoft.Data.Sqlite and the output of our code, but compared to others, this was not easy to achieve based on these bug reports. So the contribution is that it will help someone (myself included) to help out that the “Write to read-only database” error could have been caused by deleting the db file while the connection is open.

 use (var New = SqliteConnection ("data source = test.db") flaw) 
 
 scam. open (); 
 var cmd = con.CreateCommand (); 
 cmd.CommandText "PRAGMA = Foreign_keys = ON"; 
 cmd.ExecuteNonQuery (); File.Delete ("/ app / test.db"); // Connection open, content cmd.CommandText = @ "CREATE TABLE [User] (id NOT varchar NULL)"; 
 cmd.ExecuteNonQuery ();

On Linux, File.Delete should succeed, but the next ExecuteNonQuery should fail. On Windows on the back, File.Delete does not work.