PHP website a message
important!just a note:weird behaviour when doing an exec on a sqlite db!!!ifWant to execute a query on a SQLite db with Exec, and your dbfile already is e.g. mode777, and youGetsome PHP errors saying"sqlite3::exec (): Unable to open database file in ...." and youGetCrazy whiledebugging, just add writeüermissions to the whole directory forThe user the webserver/PHP runs. ThisBehaviour makes absolutely NO sense, and isa source of frustration.at least a more meaningful errormessage would being nice.i couldnt figure outWhy SQLite needs Write permissions forThe whole dir instead of only one file. This isStupid and must be a bug!(To is secure you has to create a directory with Write permissions only forPhp/apache)
The main idea is: put the database into a different folder (do not affect other files), set read and Write permissions
The tangled is: the database and the database is in the folder to be writable (perhaps because the database is written, you need to create a temporary file)
The specific use is chmod
PHP SQLite permissions