Home » Database » DB_DataObject » Bug #2999
DataObject fails on find
Details
| Submitted | 2004-12-21 06:54 UTC |
|---|---|
| From | naveen at dittakavi dot com |
| Status | Bogus |
| Package | DB_DataObject |
| PHP Version | 4.3.8 |
| OS | Linux Red Hat Enterprise Server |
| Roadmaps | (Not assigned) |
Comments
[2004-12-21 06:54 UTC] naveen at dittakavi dot com
Description:
------------
I am moving an application to a virtual dedicated server at jumpline.com. I tested my pear DSN and I can log in and query using DB.php successfully. This application works successfully with another hosting provider, however I cannot seem to understand why the application fails upon executing a "find" in this scenario.
I have tried setting the Zend Optimizer values to both true and false and the error occurs under both conditions...
Reproduce code:
---------------
Code that calls upon "AttorneyOrder":
function getAllAttorneys() {
$attorneyOrder = new AttorneyOrder();
$attorneyOrder->debugLevel(5);
$attorneyOrder->orderBy('order_id');
$attorneyOrder->find();
//Entire application dies here
...}
Expected result:
----------------
The function should continue after DataObject performs a find.
Actual result:
--------------
//This is the output to the browser
attorneyorder: __find:
attorneyorder: CONNECT: NEW CONNECTION
attorneyorder: CONNECT: pgsql://username:password@/databasename 856d8b96215a35b66ce3a4cb9a8ec14c
attorneyorder: CONNECT: a:1:{s:32:"856d8b96215a35b66ce3a4cb9a8ec14c";O:8:"db_pgsql":26:{s:8:"features";a:4:{s:7:"prepare";b:0;s:8:"pconnect";b:1;s:12:"transactions";b:1;s:5:"limit";s:5:"alter";}s:13:"errorcode_map";a:0:{}s:7:"phptype";s:5:"pgsql";s:14:"prepare_tokens";a:0:{}s:13:"prepare_types";a:0:{}s:16:"prepared_queries";N;s:15:"prepare_maxstmt";i:0;s:10:"last_query";s:0:"";s:9:"fetchmode";i:1;s:22:"fetchmode_object_class";s:8:"stdClass";s:7:"options";a:7:{s:10:"persistent";b:0;s:3:"ssl";b:0;s:5:"debug";i:0;s:14:"seqname_format";s:6:"%s_seq";s:8:"autofree";b:0;s:11:"portability";i:0;s:8:"optimize";s:11:"performance";}s:3:"dbh";N;s:6:"_debug";b:0;s:19:"_default_error_mode";N;s:22:"_default_error_options";N;s:22:"_default_error_handler";s:0:"";s:12:"_error_class";s:8:"DB_Error";s:16:"_expected_errors";a:0:{}s:10:"connection";i:0;s:8:"dbsyntax";s:5:"pgsql";s:19:"transaction_opcount";i:0;s:3:"dsn";a:9:{s:7:"phptype";s:5:"pgsql";s:8:"dbsyntax";s:5:"pgsql";s:8:"username";s:8:"usernameremoved";s:8:"password";s:8:"passwordremoved";s:8:"protocol";s:3:"tcp";s:8:"hostspec";s:0:"";s:4:"port";b:0;s:6:"socket";b:0;s:8:"database";s:8:"databasename";}s:3:"row";a:0:{}s:8:"num_rows";a:0:{}s:8:"affected";i:0;s:10:"autocommit";b:1;}}
[2004-12-21 17:53 UTC] naveen at dittakavi dot com
I recofirmed my PHP version it is 4.3.8. Also the no overload is set to true before DataObject.php is included.
My other hosting company just moved to PHP 4.3.10 and all my applications including the one in quest, are working fine as of now on their servers.
Where should we go from here? I can see if I can install gdb on that machine to conduct a backtrace. Would that be helpful to you?
[2005-02-01 14:48 UTC] naveen at dittakavi dot com
Never got it to work with a virtual private server. (Jumpline.com)