Edit report at http://bugs.php.net/bug.php?id=31342&edit=1

 ID:               31342
 Updated by:       [email protected]
 Reported by:      hugo dot pl at gmail dot com
 Summary:          SQLite OO interface with Exceptions (patch included)
-Status:           Open
+Status:           Bogus
 Type:             Feature/Change Request
-Package:          Feature/Change Request
+Package:          *General Issues
 Operating System: *
 PHP Version:      5.1.0-dev
 Assigned To:      helly

 New Comment:

Upstream won't do any more work on SQLite 2. For SQLite 3 we have a
different extension so we won't do such changes for SQLite 2 anymore.


Previous Comments:
------------------------------------------------------------------------
[2005-01-11 04:27:09] hugo dot pl at gmail dot com

Maybe adding another paramater in the constructor to set this flag?



SQLiteDatabase( file, mode, errmsg, flags )

------------------------------------------------------------------------
[2005-01-10 08:46:31] [email protected]

We cannot easily do this because it would change the api compared to
5.0. So what we need to do is adding a method set_throw_exceptions(bool)
or adding a flag SQLITE_THROW_EXCEPTIONS for the result type parameter.



Once we have this we could easily extend all yout 'if (object)' checks
to test for that flag also. But we must not extend the checks in the
ctors because there we MUST throw exceptions.



------------------------------------------------------------------------
[2005-01-10 00:25:33] hugo dot pl at gmail dot com

Sorry for the delay, I was travelling.



The patch generated with "diff -u orig_file mod_file"



http://sqlitefront.sourceforge.net/temp/patch.diff

------------------------------------------------------------------------
[2005-01-01 14:27:44] [email protected]

unified diff == diff -u

------------------------------------------------------------------------
[2004-12-31 01:31:59] [email protected]

Please provide a unified patch, thanks.

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    http://bugs.php.net/bug.php?id=31342


-- 
Edit this bug report at http://bugs.php.net/bug.php?id=31342&edit=1

Reply via email to