Re: Sybase array result problems-- help!!

Pretlow, To expose some of my ignorance... Why do you use db-lib instead of ct-lib? When I began developing the application I am currently working on, I chose to use Sybase becase my client insisted on either Sybase or Oracle. I was not familiar with either; but at that time Sybase ASE 11.0.3.3 was the only completely free verson of either that I knew of, so that's what I picked. I chose to use php's ct-lib support because it was a newer package and it supported some functions that db-lib did not. By the way, I have *not* experienced the refresh problems you have. Regards, Carroll Barrett From: Pretlow L. Stevenson III <php@diamon-associates.com> To: php-db@lists.php.net <php-db@lists.php.net> Cc: php-dev@lists.php.net <php-dev@lists.php.net> Date: Monday, July 17, 2000 4:08 PM Subject: [PHP-DB] Sybase array result problems-- help!! We're currently developing a web-based php database application and are experiencing problems while fetching rows from Sybase. The array result values seem to change whenever the page is refreshed. Occassionally, the proper results will be displayed, but an additional page refresh often leads to different array values. The results often appear random, or are the contents of other array elements pulled from the database. For example, a lastname field in the returned array may contain numbers stored elsewhere in the database as opposed to actual last names. Looking over the list of reported bugs, we noticed that there are currently outstanding issues associated with the db-lib (which is what we are currently running on a unix box along with Apache). The same code worked fine over an odbc connection on a PC running Win98, PWS and an MS Access back-end, which is what led us to question Sybase. We were also able to locate several other developers who stated similar problems, as in Bug Report 5439 and 5637. We're thinking of switching over to the ct-lib which seems to be the consensus until db-lib is fixed, but first wanted to verify that such behavior has been reported for other users running db-lib; or if no reports of this nature have been experienced. Any help anyone is able to provide would be great, as we are considering switching over to ct-lib within the next two days. Thnx. -Pretlow Stevenson Comuter Associates International p.s. We apologize for posting this to both lists, but were trying to catch all possible responses by posting in both the general dev and db forums.