Changes between Version 39 and Version 40 of PySqlite

Timestamp:

Aug 24, 2009, 7:47:54 AM (15 years ago)

Author:

Christian Boos

Comment:

clarify the case for missing write permissions

PySqlite

@@ -170 +170 @@
 ==== `DatabaseError: file is encrypted or is not a database` ====
 
-Typical error seen when accessing a SQLite 2.x database file with a SQLite 3.x library.
+This somewhat ''cryptic'' error message happens when trying to modify the database file and the '''write''' permission is missing.
+
+Otherwise, this is also a typical error seen when accessing a SQLite 2.x database file with a SQLite 3.x library.
 
 See [wiki:0.10/TracUpgrade#From0.8.xto0.9].
@@ -192 +194 @@
 ==== `OperationalError: unable to open database file` ====
 
-Besides the obvious reason of missing read permissions on the file, it can also happen when the server process has already opened too many files and is unable to open new ones due to O/S limitations. See #8551 for a detailed explanation. You can tell immediately between the two causes depending on the occurrence of the error: if the error is systematic, it's a permission problem, if it's only transient and happening under load, then it's likely the second.
+Besides the obvious reason of missing '''read''' permissions on the file, it can also happen when the server process has already opened too many files and is unable to open new ones due to O/S limitations. See #8551 for a detailed explanation. You can tell immediately between the two causes depending on the occurrence of the error: if the error is systematic, it's a permission problem, if it's only transient and happening under load, then it's likely the second.
 
 ==== `OperationalError: database is locked` ====