sqlite and sqlite_last_error()

From: Date: Wed, 08 Oct 2003 18:03:06 +0000
Subject: sqlite and sqlite_last_error()
Groups: php.pecl.dev 
Request: Send a blank email to pecl-dev+get-107@lists.php.net to get a copy of this message
Is it intentional that sqlite_last_error() always returns 1, even though correct error is captured in $php_errormsg if tracking errors? For example: -cut- ini_set('track_errors', true); $conn = sqlite_open('./test.db'); $result = sqlite_query('SELECT * FROM nosuch', $conn); print '$php_errormsg = ' . "$php_errormsg \n"; print 'sqlite_last_error($conn) = ' . sqlite_last_error($conn) . "\n"; print 'sqlite_error_string(sqlite_last_error($conn)) = ' . sqlite_error_string(s qlite_last_error($conn)) . "\n"; -cut- outputs: -cut- $php_errormsg = no such table: nosuch sqlite_last_error($conn) = 1 sqlite_error_string(sqlite_last_error($conn)) = SQL logic error or missing database -cut- I found this behaviour when writing errorhandling for DB sqlite driver. -- Mika Tuupola http://www.appelsiini.net/~tuupola/

« previous php.pecl.dev (#107) next »