I am having a difficult time finding a definitive "Best Practices" for handling SQL exceptions in a web application.
I would like to gain from the experience of users on this list. For relatively simple web applications do you think it is acceptable to simply wrap SQL exceptions as Runtime exceptions and rethrow? The thinking is that is that once the app is tested and everything is working, anything that goes wrong is probably a Runtime issue. Thanks for your consideration. Mike __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
