On Wed, 2004-01-28 at 09:13, Andrew Piskorski wrote: > On Wed, Jan 28, 2004 at 03:45:50PM -0000, Bas Scheffers wrote: > > > That reminds me, how do you do a "server wide" catch for if anything > > unexpected (ie: no specific catch) goes wrong? I know (Open)ACS > > emails the > > Why would you WANT to do that? Perhaps I misunderstand your intent, > but I can't imagine any reason.
Yes, catch should not be used unless you need to do something important based on an error, like close a file that you opened, or roll back a transaction. Hiding errors from the end user isn't a good reason to use catch, and will, in the end, make it very difficult to find the cause of an error. As far as reporting the sql error, I think AOLserver has always spit out two errors: one at the sql level, and a second at the tcl level. The sql level error is what you want to look at to debug the application. Unfortunately, AOLserver shows the tcl error to the user, which isn't very specific. tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
