die() not dying....
Posted: Mon Jun 27, 2005 7:12 pm
I'm really stumped by this.
I'm having some issues with some DB queries, so turn on my query debugging code (basicly just echo-ing out all queries as the DB abstraction layer gets them) and add a die("Trouble Spot"); after the problem area. Fill out the form an submit. My code buffers the real page, so the queries appear before any reespective warning/error from the db function calls and above the buffered page.
The die() should cause the buffered page to never get displayed.
However, right now the full page displays, a large fraction of the queries, but not all upto the die point. The "Trouble Spot" from the die doesn't print, but execution in the script aborts from within the current several level tested if, but then appears to resume the flow in the script and reaches the statements to print the buffered page.
While the troublesome INSERTS never print, nor the immediately preceding one, the immedately preceding one is in the DB after the script runs (and that table was empty before)
I am currently in a slightly unusual program environment:
script called a member function of a class which then includes a "template" from outside the
webtree. The die is in this "template" file.
Any idea what could be going on? I've never had die act up before....
I'm having some issues with some DB queries, so turn on my query debugging code (basicly just echo-ing out all queries as the DB abstraction layer gets them) and add a die("Trouble Spot"); after the problem area. Fill out the form an submit. My code buffers the real page, so the queries appear before any reespective warning/error from the db function calls and above the buffered page.
The die() should cause the buffered page to never get displayed.
However, right now the full page displays, a large fraction of the queries, but not all upto the die point. The "Trouble Spot" from the die doesn't print, but execution in the script aborts from within the current several level tested if, but then appears to resume the flow in the script and reaches the statements to print the buffered page.
While the troublesome INSERTS never print, nor the immediately preceding one, the immedately preceding one is in the DB after the script runs (and that table was empty before)
I am currently in a slightly unusual program environment:
script called a member function of a class which then includes a "template" from outside the
webtree. The die is in this "template" file.
Any idea what could be going on? I've never had die act up before....