|
|
Forum Overview
::
Site Comments
|
|
|
by Entropy Stew 12/24/2002, 2:09pm PST |
|
 |
|
 |
|
The closest thing I can think of without trying to weep my way through the PHP site is for sql errores. There's a function in PHP SQL that you can call as such
$demo = mysql_fetch_array(blahblah) or die(mysql_error());
the mysql_error() function reports the exact sql error, but this has been absolutely no help I'm sure.
That's actually what I'm doing in the function that died, albeit with postgres functions. My issue is that the line # of the error comes back as being inside the function - I'd like to get a full stack trace so I can see what script is using the function as well.
-/ES/- |
|
 |
|
 |
|
|
|
|
DB chafing -- ES, get out the vaseline by niche 12/23/2002, 9:05am PST 
Re: DB chafing -- ES, get out the vaseline by Bokonon 12/23/2002, 9:44am PST 
Re: DB chafing -- ES, get out the vaseline by Entropy Stew 12/23/2002, 2:48pm PST 
Re: DB chafing -- ES, get out the vaseline by Bokonon 12/24/2002, 9:10am PST 
Re: DB chafing -- ES, get out the vaseline by Entropy Stew 12/24/2002, 2:09pm PST 
Re: DB chafing -- ES, get out the vaseline by Bokonon 12/24/2002, 11:59pm PST 
I probably need up the max number of DB backend processes by Entropy Stew 12/23/2002, 2:36pm PST 
TO up the max number. TO -nt- NT by Entropy Stew 12/23/2002, 2:37pm PST 
|
|
|
|
|