It is likely that the file can't be opened for a very predictable reason. For example, perhaps the specified path doesn't exist. (A common variation of this would be a hard coded string with single backslashes, most languages require you to escape backslashes in strings.) Perhaps the file is read only, already locked by another process, or has insufficient permissions. Most likely, this is going to be one of the regular reasons for failing to open a file.
John -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Rich Shepard Sent: Wednesday, October 21, 2009 11:52 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] Problem about write data into the DB On Wed, 21 Oct 2009, ?? wrote: > I deployed a django app on my laptop, the whole environment is like this: > the OS is UBUNTU904, the web server is Apache, and the database is > sqlite3. The deployment is success, but when I try to write some data into > the database, I get the HTTP 500 error. And I check the error log, it > shows "*OperationalError: unable to open database file*". What does this > error mean? If there are some operation permission need configure? I'd look at the django code to see where it opens the database and what happens to inform the user if that attempt fails. I know nothing about django so I cannot suggest where you should look. Rich _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
