Re: Help! Blank Screen Only, with DB_DataObjects
| From: | Justin Patrin | Date: | Tue, 01 Mar 2005 16:58:52 +0000 |
| Subject: | Re: Help! Blank Screen Only, with DB_DataObjects | ||
| References: | 1 2 3 4 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-17757@lists.php.net to get a copy of this message | ||
On Tue, 01 Mar 2005 07:23:40 -0800, dmartin-pear@mailblocks.com
<dmartin-pear@mailblocks.com> wrote:
> >> I did find something about define('DB_DATAOBJECT_NO_OVERLOAD', 1);
> >> so I tried that (before any DAOs were included), but it made no
> difference.
>
> > Are you sure this is before the *first* require of DB/DataObject.php?
>
> Yes.
> Can you tell me why some docs say to set it to 1, and others say to set
> it to 0?
As long as it's defined it doesn't matter what it is. Some people say
1, the DB_DO docs say 0 and sometimes I say true. It all works the
same.
>
> > What exactly are the PHP versions (4.3.x isn't enough)?
>
> my windows box = 4.3.3
> hosting linux box = 4.3.10
Yep, that's it. 4.3.10 has major issues with overloading. Don't *ever*
use overloading with PHP4. It *will* cause you untold amounts of
grief. Make sure that define is before the very first require of
DB/DataObject.php
>
> > Are you using mysql or mysqli?
>
> mysql
> hosting doesn't have mysqli, i don't think
>
> > Are you using any mysql 4.1 features that mysql 4.0 doesn't have?
>
> Not to my knowledge, but it sure feels that way.
> Is there any way to test that?
>
> > Have you asked the hosting company to check their web server logs for
> crashes?
>
> They gave me shell access. The server had to be restarted once last
> night, and mysql crashed once (when i was hitting my page).
>
> >> Have you asked the hosting company to check their web server logs
> for crashes?
>
> > Markus said: I've encountered exactly the same behaviour yesterday.
> It *is* the overload crap.
> > Again. I really don't know why DB_DATAOBJECT_NO_OVERLOAD doesn't
> default to 1 when PHP4 is running.
>
> I'll go read all the overload docs and see if I can do anything more
> about it.
>
--
Justin Patrin