Since posting the original copy of this message -- which, in 10 hours, never appeared
on this newsgroup -- I upgraded
from PHP version 4.3.4 to 5.0.1. Unfortunately, the same exact problem persists. I'm
starting to believe this is a bug
in PHP's MySQL memory management functions.
Original
William wrote:
Since posting the original copy of this message -- which, in 10 hours, never appeared
on this newsgroup -- I upgraded
from PHP version 4.3.4 to 5.0.1. Unfortunately, the same exact problem persists. I'm
starting to believe this is a bug
in PHP's MySQL memory management
I can accept that as a workaround, but I was hoping to do more than merely mute the
warnings. Is there a way to truly
use the connection and result set handles? Can PHP truly utilize it's own connection
resource handles in code?
Bottom Line: This is going to make a real mess when multiple
William wrote:
I can accept that as a workaround, but I was hoping to do more than merely mute the
warnings. Is there a way to truly
use the connection and result set handles? Can PHP truly utilize it's own connection
resource handles in code?
Bottom Line: This is going to make a real mess
If you read the code I posted, you'd see that I am sending valid resources. :) As I
explained, I lifted the technique
directly from the PHP documentation. Now, if you can see a bug in my implementation
of this technique, by all means,
please point it out.
--
--
William Kimball, Jr.
William wrote:
If you read the code I posted, you'd see that I am sending valid resources. :) As I
explained, I lifted the technique
directly from the PHP documentation. Now, if you can see a bug in my implementation
of this technique, by all means,
please point it out.
Please limit replies
Why waste time by turning this into an attack? (A rhetorical question, please don't
bother addressing it.)
I'm pressing for a better answer now because the workaround you posted simply ignores
the problem and because you implied
that you got these functions to work -- presumably without having
William wrote:
Why waste time by turning this into an attack? (A rhetorical question, please don't
bother addressing it.)
I'm pressing for a better answer now because the workaround you posted simply ignores
the problem and because you implied
that you got these functions to work -- presumably
William wrote:
Why waste time by turning this into an attack? (A rhetorical question, please don't
bother addressing it.)
I'm pressing for a better answer now because the workaround you posted simply ignores
the problem and because you implied
that you got these functions to work -- presumably
John Holmes wrote:
Programming languages do not make things up. If you say
mysql_close($anyvariable) and PHP says that $anyvariable is not a MySQL
connection resource, then it's not.
No, it's not. Shh. It's not.
If you can reduce what you're seeing to the smallest amount of code
possible and
The problem turned out to be a run-time bug with object instances (of the same class)
stepping on each other. More
specifically, PHP doesn't seem to differentiate between a flat script-level $ovConn
object and a new instance of $ovConn
that gets fired up in an unrelated object's method at
William wrote:
snip
Please keep your responses professional; this newsgroup/list is the first contact for people needing help with PHP --
even if it's their own fault. Your enflamed, emotionally charged reactions help no one and seem only to serve your own
ego. This matter is closed. Good day.
12 matches
Mail list logo
