No! The problem is this differs from system to system.
I thought most systems allow read during write and implemented it the
test this way until i had a solution for the extension to disallow read
during write.
I must disallow it because most libraries have problems (flushing of data).
So that the results are not as expected. I hope i can commit a solution
to this tody. Should i commit the expected test results already now?
marcus
At 19:52 13.11.2002, Derick Rethans wrote:
---------- Forwarded message ----------
Date: 13 Nov 2002 18:32:03 -0000
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [PHP-QA] Test results
================================================================================
/opt/DEV/php/php4/ext/dba/tests/dba_gdbm.phpt
================================================================================
---- EXPECTED OUTPUT
database handler: gdbm
3NYNYY
Content String 2
Content 2 replaced
Read during write permitted
Content 2 replaced 2nd time
The 6th value
array(3) {
["key number 6"]=>
string(13) "The 6th value"
["key2"]=>
string(27) "Content 2 replaced 2nd time"
["key5"]=>
string(23) "The last content string"
}
---- ACTUAL OUTPUT
database handler: gdbm
3NYNYY
Content String 2
Content 2 replaced
Cannot read during write operation
Content 2 replaced 2nd time
The 6th value
array(3) {
["key number 6"]=>
string(13) "The 6th value"
["key2"]=>
string(27) "Content 2 replaced 2nd time"
["key5"]=>
string(23) "The last content string"
}
---- FAILED
================================================================================
005- Read during write permitted
005+ Cannot read during write operation
================================================================================
I think this just fails because the error message changed?
Derick
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
