Save the queries on different files, one for each query. Then make a
script that will read all these files and execute the queries, maybe run it
as a cron job, and delete the succesful ones . With several files will be
easier to spot an error if occur, just open it and see the query.

  Okay, it's not much 'on-the-fly', because doesn't have all agreggated
processes from the whole script running, but your queries will be tested...


Julio Nobrega

No matter where you go, &this.

"Steven Roussey" <[EMAIL PROTECTED]> wrote in message
news:003001c17844$9c7b9aa0$[EMAIL PROTECTED]...
> > You could just exec() the page again, with a parameter telling it to
> use
> > the test server, like so:
> I like this general idea, though the above method would take a little
> more work since I would have to pass the environment variables and
> apache variables (GET and POST, etc) to exec and I don't know how.
> However, I can try and setup a test web server on the test SQL server
> and have a auto_postpend file that sets up all these variables (cookies,
> post vars, etc) and sends them off using fsockopen, etc., as a HTTP
> request to the other server. If I setup the other server to ignore
> hangups, then I can send the request and quit.
> Thanks for the idea!
> Sincerely,
> Steven Roussey

PHP General Mailing List (
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to