Re: Very Strange DB_DataObject error
| From: | Matt Mitchell | Date: | Fri, 16 Apr 2004 02:15:20 +0000 |
| Subject: | Re: Very Strange DB_DataObject error | ||
| References: | 1 2 3 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-11898@lists.php.net to get a copy of this message | ||
Whew! Found the problem and it now works! Actually it's all here: http://pear.php.net/bugs/bug.php?id=47
Matt
Matt Mitchell wrote:
Hi, I tried to change the memory_limit but this php installation wan't compiled with that option. The php version however is 4.3.4. My class name is dataobject_product and the method I'm guessing is 'find' and/or 'get'. Any other ideas? Thanks for your help! Matt Justin Patrin wrote:Matt Mitchell wrote:I had things working nicely on my testing server, and when I uploaded to the live server, things went bad. Before setting the debug level to 5, as soon as I would call $dbObject->find() OR $dbObject->get(), the page loading would completely stall and the browser/server wouldn't even render the page errors. I turned debug level on to 5, and then saw a strange error when ever trying to call those 2 methods. Here it is: Code: Warning: unable to call dataobject_product::Œ”{e() method in /resources/php_lib/pear/DB/DataObject.php on line 371 dataobject_product: CONNECT: USING CACHED CONNECTION The funny thing is that everytime I re-load the page, the method here called Œ”{e changes to another completely random method name using very odd characters. The next one was: t<„e and the next: \Û§e Does anyone know what this is coming from? If I use a raw query using the Pear DB object things work find. If I use DB_DataObject::count() everything works fine. I looked at the code on the line specified, but no way I can figure things out with the time I have (err, don't have), and I figure it's got to be something more or less related to general php (the environment?). Maybe not? MattSounds kind of like an error I was having when dealing with the SOAP server. How long are your class names? I found that if the length of the class name and function name together was too large, then PHP would have errors like that. Also, check your memory maximum.