Re: DB_DataObject multiple insert problem. MORE INFO
| From: | MFriedman at symcor dot com | Date: | Sun, 06 Jul 2003 16:22:23 +0000 |
| Subject: | Re: DB_DataObject multiple insert problem. MORE INFO | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-18050@lists.php.net to get a copy of this message | ||
I'm just checking everything into cvs now so I can check it out onto
another server with a different php version.
When I had debugLevel(1) I just saw the insert done once - since the
problems appear to be happening after shutdown - you won't see any useful
debugging output (in the browser) unless you can log the debug output.
Here's something even wierder:
I created a shutdown function that simply logs the words: "SHUTDOWN
FUNCTION CALLED." to a file. This function gets called multiple times. The
log gets written to multiple times [before and after page shutdown] - Very
Very Strange.
I'm going to keep working on it - I'll try to find out if this is a problem
exclusive to DataObject or if I can reproduce it without invoking
DataObject.
Keep the thoughts and info coming. Thanks!
Matt Friedman.
Markus Wolff
<wolff@21st.de> To: MFriedman@symcor.com
cc: pear-dev@lists.php.net, Alan Knowles
<alan@akbkhome.com>
06/07/2003 12:17 Subject: Re: [PEAR-DEV] DB_DataObject multiple insert
problem. MORE INFO
PM
MFriedman@symcor.com wrote:
> Markus and Alan:
>
> This is worth tracking down I think. Do you happen to be using php4.3..1?
(I
> am) I haven't narrowed down the problem yet, so I don't know if it's a
php
> version issue or a DataObjects issue. But something odd is happening and
if
> it is happening for Markus too, then something is up.
What I can say now is that on the server in question, the PHP version
is 4.3.1 as well. I have access to that server only at work though, so
I can´t test anything today.
I have set up a small script on friday that tries to do the bogus
operations without Flash and AMFPHP involved, so I´ll try that one
tomorrow with DataObject´s debug level set to 1.
Have you tried to set debug to 1 already? If so, what was the output?
Regards,
Markus