|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2010-06-06 21:52 UTC] hajo at csphere dot eu
-Summary: open_basedir restrictions mismatch on vaccum command
+Summary: open_basedir restrictions mismatch on vacuum command
[2010-06-06 21:52 UTC] hajo at csphere dot eu
[2010-06-09 18:04 UTC] iliaa@php.net
[2010-06-09 18:05 UTC] iliaa@php.net
-Status: Open
+Status: Closed
-Assigned To:
+Assigned To: iliaa
[2010-06-09 18:05 UTC] iliaa@php.net
[2010-06-20 02:09 UTC] hajo at csphere dot eu
[2010-06-20 16:12 UTC] felipe@php.net
[2010-06-20 16:25 UTC] felipe@php.net
|
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Sun Nov 09 04:00:01 2025 UTC |
Description: ------------ with open_basedir enabled and an sqlite3 database file within one of these allowed directories - using the sqlite3 extension - the sql command "vacuum <insert_tablename_here>" triggers an open_basedir restriction error. what confuses the most is that File() in the error message seems to be empty every time this error occurs and i haven't discovered such behavior in similar problems. pdo_sqlite extension is also affected, sqlite3 lib version is 3.6.22 Test script: --------------- $sqlite3->query('vacuum <anytable>'); Expected result: ---------------- no error returned Actual result: -------------- PHP-Warning: Warning: SQLite3::query() [sqlite3.query]: open_basedir restriction in effect. File() is not within the allowed path(s): (<a lot of paths listed in here>) in test.php on line 77 PHP-Warning: Warning: SQLite3::query() [sqlite3.query]: Unable to execute statement: not authorized in test.php on line 77