Edit report at http://bugs.php.net/bug.php?id=51295&edit=1
ID: 51295 Updated by: fel...@php.net Reported by: magical...@php.net Summary: SQLite3::busyTimeout not existing -Status: Feedback +Status: Closed Type: Feature/Change Request Package: SQLite related Operating System: Linux Gentoo 2.6.33 PHP Version: 5.3SVN-2010-03-14 (SVN) Assigned To: scottmac New Comment: Implemented. Previous Comments: ------------------------------------------------------------------------ [2010-06-21 13:06:33] il...@php.net Automatic comment from SVN on behalf of iliaa Revision: http://svn.php.net/viewvc/?view=revision&revision=300631 Log: MFB: Implemented FR #51295 (SQLite3::busyTimeout not existing). (Mark) ------------------------------------------------------------------------ [2010-06-20 17:30:51] paj...@php.net Automatic comment from SVN on behalf of pajoye Revision: http://svn.php.net/viewvc/?view=revision&revision=300614 Log: - #51295, SQLite3::busyTimeout not existing ------------------------------------------------------------------------ [2010-06-20 17:28:08] paj...@php.net Can you create a valid phpt for the test please? ------------------------------------------------------------------------ [2010-06-09 09:29:33] ncoesel at dealogic dot nl When using an Sqlite database from multiple processes there should always be a busy timeout. However this still doesn't prevent Sqlite from exiting prematurely. I posted a patch in bug report #51680 (which really is not a duplicate!!!) that also solves that problem. ------------------------------------------------------------------------ [2010-06-07 07:00:55] magical...@php.net Ok, I had some troubles to make a meaningful test for this bug (the php function is just calling the equivalent sqlite function), but in the end I got this. http://ookoo.org/svn/snip/20100607_php_test_bug51295.php (didn't manage to attache this to this bug report, even renamed as .txt) Anyway here it is. It forks, open a sqlite file and locks it, then the other process will try to access it with a 1 second busyTimeout then dumps the waited time and the result (should have failed with a 1 second delay with +/- 10ms) Remaining steps includes converting this test to phpt and run it once to get the "right" output (I'll need to check doc to find the right format for phpt since it's been a while). ------------------------------------------------------------------------ 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=51295 -- Edit this bug report at http://bugs.php.net/bug.php?id=51295&edit=1
