note 111114 added to sqlite3.exec

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) ---- Server IP: 213.172.110.14 Probable Submitter: 79.216.198.40 ---- Manual Page -- http://php.net/manual/en/sqlite3.exec.php Edit -- https://master.php.net/note/edit/111114 Del: integrated -- https://master.php.net/note/delete/111114/integrated Del: useless -- https://master.php.net/note/delete/111114/useless Del: bad code -- https://master.php.net/note/delete/111114/bad+code Del: spam -- https://master.php.net/note/delete/111114/spam Del: non-english -- https://master.php.net/note/delete/111114/non-english Del: in docs -- https://master.php.net/note/delete/111114/in+docs Del: other reasons-- https://master.php.net/note/delete/111114 Reject -- https://master.php.net/note/reject/111114 Search -- https://master.php.net/manage/user-notes.php