note 111114 deleted from sqlite3.exec by cmb

Note Submitter: info at tellmatic dot org ---- 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)