#19528 [Csd]: odbc_fetch_row() doesn't returned true if there is one row only

From: Date: Tue, 24 Jun 2003 15:25:53 +0000
Subject: #19528 [Csd]: odbc_fetch_row() doesn't returned true if there is one row only
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-42445@lists.php.net to get a copy of this message
ID: 19528 User updated by: scott at abcoa dot com Reported By: scott at abcoa dot com Status: Closed Bug Type: ODBC related Operating System: AIX (UNIX) PHP Version: 4.2.2 New Comment: Then the matter is settled. It would have been so cool to have table in text file where everything is arrange by x and y, just like the spreadsheet for an example. If everyone use this then we wouldn't have much need for thousands of database softwares. Previous Comments: ------------------------------------------------------------------------ [2003-06-24 10:21:14] kalowsky@php.net Sniper you like me, you really like me :) I won't open the can of worms that is remove the --with-ibm-db2 option until I have a more viable solution then what is currently enabled. So for those of you reading this in the future, worry not (yet)! ------------------------------------------------------------------------ [2003-06-23 21:14:05] sniper@php.net Like Mr. Kalowsky said, people should be using unixODBC anyway with IBM DB2 (if they even suggest that themselves too, we really should consider removing the not-so-good DB2 support altogether..?) Closing this for now. If someone else thinks it's worth to fix this, feel free to open new report..and donate some money to Dan. :) ------------------------------------------------------------------------ [2003-06-20 11:24:33] scott at abcoa dot com I was going to close this bug until I saw that there is 3 people out of 3 who are able to reproduce this problem. So, I decided to leave this open unless otherwise is closed by the developer at php.net because there are other people out there who are still struggling with this and are not as fortunate. The reason I'm going to close this bug is because I'm dumping IBM DB2 and make the move to Relexus Linter (DB software in Russia). It became appearant that it is a better software than IBM DB2 in many ways. Linter is smaller, use less maintainance, less headache, cost less, less problem with license, use less memory and work much faster on the same machine regardless of whether the table in the database is very large or not. Good Luck! Scott ------------------------------------------------------------------------ [2003-03-11 08:49:39] scott at abcoa dot com Lost track of time, so sorry about that. What we're going to need is more people who are experiencing this problem. In answer to your question, I'm not sure if it is a driver issue or not because I have not upgraded the AIX nor have I upgraded the DB2 driver nor have I upgraded the DB2 software. I'm waiting for version 9.1 to come out and buy it, whew, it's a pretty expensive software. The only thing changes from that time of version 4.0.6 to 4.2.3 was the inclusion of the '--with-mcrypt' option to the configure command but this doesn't seem to be the cause of the problem because they are not related. We had one other user in this bug report who reported this problem. So, go ahead and put this bug in inactive status or something until someone can step forward with the problem. I don't have a solution to this problem. Thanks, Scott P.S. I have noticed that PHP have a built-in programming script that allow PHP to create a formatting and datas into a PDF then generate a PDF file. Maybe PHP developers can do that similar thing by coming up with some ideas to create a PHP Database or a PHP CVS file that can act as a database. The logic shouldn't be too difficult to come up with and it could help to depend less on the 3rd party database and instead more on the PHP. It is just an idea but not a bad idea... I would love to hear about it one day. ------------------------------------------------------------------------ [2003-03-10 20:41:10] sniper@php.net No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. ------------------------------------------------------------------------ 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/19528 -- Edit this bug report at http://bugs.php.net/?id=19528&edit=1

« previous php.bugs (#42445) next »