There is a database-based application at work with an authorization system. If a user is not logged in, the only system accessible to them is the authorization system where they must provide a valid username and password that are stored in the database.
The login function has the following comment in it:
// NOTE: This is the only place in the program that will given an error about // the DSN not being properly configured/connected, because this is the only // place where that is a cause for concern - the other queries can only be // accessed once the user is logged in, and once they are logged in, they // obviously have a valid connection to the database.
Indeed, the other queries in this program do not include a detailed error displayed to the user about a database failure; if there is any sort of error, it is silently logged to a file for the IT and programming staff to analyze.
Is this a good design decision?