php sqlite 許可權

標籤：

php官網一段留言

IMPORTANT! just a note: weird behaviour when doing an exec on a sqlite db!!!if want to execute a query on a sqlite db with exec, and your dbfile already was e.g. mode 777, and you get some php errors saying"SQLite3::exec(): unable to open database file in ...."and you get crazy while debugging, just add write üermissions to the whole directory for the user the webserver/php runs.this behaviour makes absolutely NO sense, and is a source of frustration.at least a more meaningful errormessage would be nice.i couldnt figure out why sqlite needs write permissions for the whole dir instead of only one file. this is stupid and must be a bug!(to be secure you have to create a directory with write permissions only for php/apache)

大意是：把資料庫放到一個另外檔案夾（不影響其他檔案），設定讀寫權限

糾結的是：資料庫和資料庫所在的檔案夾都要可寫（可能是因為寫資料庫時，需要建立一個臨時檔案）

具體用到就是 chmod

php sqlite 許可權