Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.5.0b4

Bug #9828 No check for extension
Submitted: 2007-01-14 16:45 UTC
From: yunosh Assigned: quipo
Status: Closed Package: MDB2_Driver_sqlite (version 1.3.0)
PHP Version: Irrelevant OS:
Roadmaps: (Not assigned)    
Comments Add Comment Add patch

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 : 45 - 42 = ?

 [2007-01-14 16:45 UTC] yunosh (Jan Schneider)
Description: ------------ The driver doesn't check if the sqlite extension is loaded. And even worse, there are silenced sqlite_last_error() calls in errorInfo() that result in a fatal error without any further notice. For the end user, the script simply stops. I didn't check if other drivers are affected too.


 [2007-03-05 00:58 UTC] quipo (Lorenzo Alberton)
Actually, there is this check in connect(): if (!PEAR::loadExtension($this->phptype)) regarding the fatal error, can it be related to this bug? Can you try the CVS version, and tell me if you still experience this issue?
 [2007-03-05 16:06 UTC] yunosh (Jan Schneider)
Yes, this pretty much sounds like bug #9800. I'm gonna try a CVS checkout now.
 [2007-03-05 16:32 UTC] yunosh (Jan Schneider)
No, CVS doesn't make a difference.
 [2007-03-05 20:40 UTC] quipo (Lorenzo Alberton)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. -- An error in MDB2_Driver_sqlite::getConnection() wasn't propagated to the caller methods.