php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #19075 rows repeat in result
Submitted: 2002-08-23 11:40 UTC Modified: 2002-08-28 12:12 UTC
From: tho at e-dict dot net Assigned:
Status: Not a bug Package: Adabas-D related
PHP Version: 4.2.1 OS: Linux
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: tho at e-dict dot net
New email:
PHP Version: OS:

 

 [2002-08-23 11:40 UTC] tho at e-dict dot 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?

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-08-23 14:49 UTC] georg@php.net 
Could you add a little script (and the database definition) please.
 [2002-08-26 12:08 UTC] tho at e-dict dot 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-28 12:12 UTC] kalowsky@php.net 
marking as bogus.  If you decide that this ia valid PHP bug later, do please re-open it.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Mon Dec 30 14:01:28 2024 UTC