#19075 [Opn->Bgs]: rows repeat in result
| From: | kalowsky@php.net | Date: | Wed, 28 Aug 2002 16:12:28 +0000 |
| Subject: | #19075 [Opn->Bgs]: rows repeat in result | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-18045@lists.php.net to get a copy of this message | ||
ID: 19075
Updated by: kalowsky@php.net
Reported By: tho@e-dict.net
-Status: Open
+Status: Bogus
Bug Type: Adabas-D related
Operating System: Linux
PHP Version: 4.2.1
New Comment:
marking as bogus. If you decide that this ia valid PHP bug later, do
please re-open it.
Previous Comments:
------------------------------------------------------------------------
[2002-08-26 12:08:17] tho@e-dict.net
I tried to recreate the bug using a test database and found out that
the part I paraphrased with "print_r($row)" contains a commited
transaction itself. Since we use persistent database connections and do
a rollback all the time before starting a new transaction the query I'd
like to display was rolled back and the only thing I can blaim php for
is to not complaining abount using a result handle of a rolled back
query. I leave the bug open since I cannot decide if this is the
desired behaviour.
I'll try to check my code more detailed if future before submitting a
bug. I sorry for wasting your time.
so long tho
------------------------------------------------------------------------
[2002-08-23 14:49:54] georg@php.net
Could you add a little script (and the database definition) please.
------------------------------------------------------------------------
[2002-08-23 11:40:58] tho@e-dict.net
that's short what I do:
$sql = "select * from table a";
odbc_execute...
while (odbc_fetch_into...) {
print_r($row);
}
the first rows are correct but then fetch_into returns the same row
over and over again until num_rows is reached.
the longer the row the faster this happens, looks like a static
buffer.
The result is something like this
rowid field1 field2
1 1
2 2
3 3
.
.
.
60 60 content60
61 60 content60
62 60 content60
The behaviour is hard to explain and there are enough cases where
everything is just fine even with really lot of rows.
the error happens with adabas 12 and we have trouble with this with
adabas 11 and php 3.0.7 too.
is this a php-bug or is there an option to increase a buffer or is this
a bug in adabas' odbc-library?
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=19075&edit=1