Bug #73530 [ReO->Asn]: Unsetting result set may reset other result set

From: Date: Tue, 24 Oct 2017 05:26:53 +0000
Subject: Bug #73530 [ReO->Asn]: Unsetting result set may reset other result set
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-211952@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=73530&edit=1 ID: 73530 Updated by: kalle@php.net Reported by: cmb@php.net Summary: Unsetting result set may reset other result set -Status: Re-Opened +Status: Assigned Type: Bug Package: SQLite related Operating System: * PHP Version: master-Git-2016-11-15 (Git) Assigned To: cmb Block user comment: N Private report: N Previous Comments: ------------------------------------------------------------------------ [2017-01-20 15:13:07] it-solutions at schultz dot ch I can confirm that PHP 5.6.30 (in my environment) successfully fixed this issue (tested against PHPExcel library using SQLite3 caching method) Thanks for the work! ------------------------------------------------------------------------ [2017-01-13 10:39:18] cmb@php.net > Please keep in mind that this is also an issue on 5.6.xx and not > only on 7.0.xx/7.1.0! The revert of the BC breaking commit is already in PHP 5.6.30RC1, and as such is supposed to be shipped with PHP 5.6.30. ------------------------------------------------------------------------ [2017-01-13 10:25:27] nikolay dot petkov at peri dot de Working: PHP 5.6.28 Fails: PHP 5.6.29 I have encountered the same issue with one of our deployed applications that uses the PHPOffice/PHPExcel library to generate Excel part lists. After the PHP has been updated on the server, the application crashes due to the bug fix and the external library. Please keep in mind that this is also an issue on 5.6.xx and not only on 7.0.xx/7.1.0! For now I have to rewrite the application to use another cache method... ------------------------------------------------------------------------ [2016-12-29 15:19:38] jcrews at gridlox dot net >Thanks for reporting! > >> It appears, via static analysis, the correct solution is to >> sqlite3_reset and sqlite3_clear prior to re-binding parameters >> in sqlite3stmt::execute (in addition to this change). > >That doesn't appear to solve the issue with your supplied test >script. I'm not yet sure why, but probably it hasn't been a good >idea to try to resolve this issue in a patch release anyway, so >I'm going to revert the fix for now. I will be a good OSS citizen and work on a solution for 7.1.x. Thank you for reverting in the interim. ------------------------------------------------------------------------ [2016-12-29 13:03:01] cmb@php.net Automatic comment on behalf of cmbecker69@gmx.de Revision: http://git.php.net/?p=php-src.git;a=commit;h=2ba3b275948050ce600c5234b66e840b640ca5a5 Log: Revert "Fix #73530: Unsetting result set may reset other result set" ------------------------------------------------------------------------ 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 https://bugs.php.net/bug.php?id=73530 -- Edit this bug report at https://bugs.php.net/bug.php?id=73530&edit=1

« previous php.bugs (#211952) next »