Change SQLite database mode to read-write

Question

How can I change an SQLite database from read-only to read-write   When I executed the update statement  I always got      SQL error  attempt to write a readonly database   The SQLite file is a writeable file on the filesystem

User · Answer

From the command line  enter the folder where your database file is located and execute the following command   chmod 777 databasefilename   This will grant all permissions to all users

User · Answer

In the project path  Terminal django project    sudo chown django django

User · Answer

I solved this by changing owner from root to me on all files on  db dir   Just do ls -l on that folder  if any of the filer is owned by root just change it to you  using  sudo chown user file

User · Answer

In Linux command shell  I did    chmod 777  lt db folder gt    Where  contains the database file    It works  Now I can access my database and make insert queries

User · Answer

Edit the DB  I was having problems editing the db  I ended up having to  sudo chown  non root username  ts3server sqlitedb as long as it wasn t root  i could edit the file  Username is the username of my non root account    Auto start TeamSpeak  as your non root account     crontab -e  reboot      path to ts3server  aka  home ts3server ts3server startscript sh start

User · Answer

This error usually happens when your database is accessed by one application already  and you re trying to access it with another application

User · Answer

On Ubuntu  change the owner to the Apache group and grant the right permissions  no  it s not 777    sudo chgrp www-data  lt path to db sqlite3 gt  sudo chmod 664  lt path to db sqlite3 gt    Update  You can set the permissions for group and user as well   sudo chown www-data www-data  lt path to db sqlite3 gt

User · Answer

On Linux  give read write permissions to the entire folder containing the database file   Also  SELinux might be blocking the write  You need to set the correct permissions   In my SELinux Management GUI  on Fedora 19   I checked the box on the line labelled httpd unified  Unify HTTPD handling of all content files   and I was good to go

User · Answer

To share personal experience I encountered with this error that eventually fix both  Might not necessarily be related to your issue but it appears this error is so generic that it can be attributed to gazillion things    Database instance open in another application  My DB appeared to have been in a  locked  state so it transition to read only mode  I was able to track it down by stopping the a 2nd instance of the application sharing the DB  Directory tree permission - please be sure to ensure user account has permission not just at the file level but at the entire upper directory level all the way to   level    Thanks

User · Answer

On Windows   tl dr  Try opening the file again   Our system was suffering this problem  and it definitely wasn t a permissions issue  since the program itself would be able to open the database as writable from many threads most of the time  but occasionally  only on Windows  not on OSX   a thread would get these errors even though all the other threads in the program were having no difficulties   We eventually discovered that the threads that were failing were only those that were trying to open the database immediately after another thread had closed it  within 3 ms    We speculated that the problem was due to the fact that Windows  or the sqlite implementation under windows  doesn t always immediately clean up up file resources upon closing of a file   We got around this by running a test write query against the db upon opening  e g   creating then dropping a table with a silly name    If the create drop failed  we waited for 50 ms and tried again  repeating until we succeeded or 5 seconds elapsed   It worked  apparently there just needed to be enough time for the resources to flush out to disk

User · Answer

I had this problem today  too    It was caused by ActiveSync on Windows Mobile - the folder I was working in was synced so the AS process grabbed the DB file from time to time causing this error

User · Answer

this error message is typically misleading  and is usually a general permissions error   On Windows   If you re issuing SQL directly against the database  make sure whatever application you re using to run the SQL is running as administrator If an application is attempting the update  the account that it uses to access the database may need permissions on the folder containing your database file  For example  if IIS is accessing the database  the IUSR and IIS IUSRS may both need appropriate permissions  you can try this by temporarily giving these accounts full control over the folder  checking if this works  then tying down the permissions as appropriate

User · Answer

If using Android   Make sure you have added the permission to write to your EXTERNAL STORAGE to your AndroidManifest xml   Add this line to your AndroidManifest xml file above and outside your  lt application gt  tag    lt uses-permission android name  android permission WRITE EXTERNAL STORAGE   gt    This will allow your application to write to the sdcard  This will help if your EXTERNAL STORAGE is where you have stored your database on the device

User · Answer

There can be several reasons for this error message    Several processes have the database open at the same time  see the FAQ   There is a plugin to compress and encrypt the database  It doesn t allow to modify the DB  Lastly  another FAQ says   Make sure that the directory containing the database file is also writable to the user executing the CGI script   I think this is because the engine needs to create more files in the directory  The whole filesystem might be read only  for example after a crash  On Unix systems  another process can replace the whole file

[sqlite] Change SQLite database mode to read-write

Examples related to sqlite