Re: Re: Re: How to calculate development time?

I am however a bit worried about MySQL development on a remote host with no error logs. Is there any way I can see what is not working without the ubiquitous Internal Server Error message?

Yes;
use CGI::Carp qw/fatalsToBrowser/;

This prints nice error messages to the browser; however, if your script dies before compiling, you just get a (fairly) unhelpful "compile error."

If you don't have a command line, maybe you can do your developing on another box somewhere and then move everything to your host? I personally could not bear to write any decently sized script without the debugger.

Comment on Re: Re: Re: How to calculate development time? Download Code

Replies are listed 'Best First'.
Re: Re: Re: Re: How to calculate development time? by Siddartha (Curate) on May 31, 2001 at 19:03 UTC
Thanks, I'll try that. I do have a development box, so I can make sure that the syntax is correct and it can compile. I will need to test to see if this solves all my problems (probably not), but thanks for the input. My biggest problem however is not the Perl errors, but possible mySQL errors. I need to set up a testing environment with MySQL and start playing around, but I have no idea what is going to happen if MySQL has problems. Will MySQL return error codes to the CGI that I can catch, or will it just die? thanks for everyone's input. the whole thing doesn't seem so impossible anymore. -Siddartha	[reply]
Re:(5) How to calculate development time? by Cirollo (Friar) on May 31, 2001 at 19:42 UTC
You should take a look at the Tricks with DBI node by btrott; it goes into some detail about error codes with DBI. MySQL should never "just die"; you might run into things like not being able to execute a bad SQL statement, but you should be able to get all the error details you need through the DBI module.	[reply]


Your skill will accomplish what the force of many cannot
	PerlMonks