Bug #15664 Updated: dba_firstkey() isn't returning the first key

ID: 15664 Updated by: caperry@webofficenow.com -Summary: dba_firstkey() isn't returning the first key Reported By: caperry@webofficenow.com -Status: Feedback +Status: Open Bug Type: DBM/DBA related Operating System: Linux PHP Version: 4.1.1 New Comment: Well, it figures that after I open a bug I can't reproduce it. 8^) It does appear to be random, as we never see it in testing, but when the code is being pounded on by a few people at once, it's more frequent. All the code I have is rather large and complicated. I can give some senarios: We use a GDBM file as a log for file transfers. When clearing the log, we do a dba_firstkey and check if it's OKay to be deleted. If it is, we delete the key and do a dba_firstkey again. A lot of times the first few items are skipped this way. We have another piece of code the pulls "big" (greater than 100 chars) values out of a database and puts 10 of them in a GDBM file. Again, it occasionally skips the first one or two. I have some example code, but as I said - it seems to work right now. Previous Comments: ------------------------------------------------------------------------ [2002-02-21 14:23:23] mrobinso@php.net Can you attach a short, concise snippet of code I can use to reproduce this please? ------------------------------------------------------------------------ [2002-02-21 14:18:06] caperry@webofficenow.com Using dba with the gdbm backend. Creating a new database and inserting 10 values. When I go to look at that database using a dba_firstkey() followed by a series of dba_nextkey() calls, I do not get back all the data. If I ask for specific keys that did not show up, they exist and have data. Any ideas? ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=15664&edit=1