#47257 [Asn->Csd]: SQLite3->__construct has no sane way to detect errors

ID: 47257 Updated by: scottmac@php.net Reported By: cellog@php.net -Status: Assigned +Status: Closed Bug Type: SQLite related Operating System: * PHP Version: 5.3.0beta1 Assigned To: scottmac New Comment: This bug has been fixed in CVS. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. Thank you for the report, and for helping us make PHP better. Previous Comments: ------------------------------------------------------------------------ [2009-02-01 17:51:57] scottmac@php.net I'll add an error mode option and probably default it to an exception. I'm not a huge fan of heavy exception throwing code, you end up wrapping huge blocks of code in try {}. ------------------------------------------------------------------------ [2009-02-01 17:22:53] crrodriguez at suse dot de Exceptions only IMHO, it is a "new" OOP only extension, kinda odd that it throws only notices on errors... ------------------------------------------------------------------------ [2009-01-31 19:22:22] cellog@php.net Description: ------------ SQLite3->__construct does not indicate errors by anything other than an E_NOTICE. This means we have to set a user error handler just to tell whether or not this code succeeds: <?php $a = new SQLite3('/path/to/database.sqlite'); ?> the constructor should throw an exception, or provide an error string parameter by reference like the SQLite object. Reproduce code: --------------- <?php // run as non-root $a = new SQLite3('/root/database.sqlite'); ?> Expected result: ---------------- exception Actual result: -------------- E_NOTICE error ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=47257&edit=1