Toby,Yep, that too. Basically, if you're already caiprutng output, it's a way to capture debugging output without having to open another stream for writing to a file.Sure, if you're running PHP code a print statement isn't that difficult. But yeah, a batch job, or other shell script .again, you could just use a print statement. But this gives another option, and set the level of the stack lower it has to GET to MySQL, and print the statement. Useful for folks who run PHP code saying this query doesn't work! and it ends up being that they can't connect ..Usually I say:1) print debug statements, and run those on the command line to see if the query itself works2) try logging in manually to the machine, from the machine you're trying to use.now they can1) encapsulate the query in a SELECT string query and see if that works.It will still fail if the user can't connect, but people are weird about printing debug statements.

Toby,Yep, that too. Basically, if you're already caiprutng output, it's a way to capture debugging output without having to open another stream for writing to a file.Sure, if you're running PHP code a print statement isn't that difficult. But yeah, a batch job, or other shell script .again, you could just use a print statement. But this gives another option, and set the level of the stack lower it has to GET to MySQL, and print the statement. Useful for folks who run PHP code saying this query doesn't work! and it ends up being that they can't connect ..Usually I say:1) print debug statements, and run those on the command line to see if the query itself works2) try logging in manually to the machine, from the machine you're trying to use.now they can1) encapsulate the query in a SELECT string query and see if that works.It will still fail if the user can't connect, but people are weird about printing debug statements.

Baz Option