|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #62288 Decouple mysql backend from sqlite3
Submitted: 2012-06-11 07:43 UTC Modified: 2012-06-13 21:47 UTC
From: HMWiesinger at gmx dot at Assigned: patrickallaert (profile)
Status: Closed Package: APM (PECL)
PHP Version: 5.4.3 OS: Linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem:
38 + 7 = ?
Subscribe to this entry?

 [2012-06-11 07:43 UTC] HMWiesinger at gmx dot at
Currently, if the path for the sqlite database does not exist or is not writable, 
apm is disabled completely, even if the sqlite backend is disabled.
This means that even though mysql is enabled, no error is logged there.

Better would be to handle the backends separately and only disable the ones that 
cannot be used, or at least don't check for the sqlite database path usability if 
the sqlite backend is disabled.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2012-06-11 07:45 UTC]
-Assigned To: +Assigned To: patrickallaert
 [2012-06-13 21:42 UTC]
Automatic comment from SVN on behalf of patrickallaert
Log: Fixed #62288: Decouple mysql backend from sqlite3
 [2012-06-13 21:47 UTC]
-Status: Assigned +Status: Closed
 [2012-06-13 21:47 UTC]
This bug has been fixed in SVN.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at

 For Windows:
Thank you for the report, and for helping us make PHP better.

Fixed in SVN / Github.

Will be part of APM 1.1.0beta5
PHP Copyright © 2001-2022 The PHP Group
All rights reserved.
Last updated: Fri Jan 28 00:03:34 2022 UTC