at a high level, doesn't this make sense though? the library author knows whether their code can recover from a certain exception, but they don't know how impor

at a high level, doesn't this make sense though? the library author knows whether their code can recover from a certain exception, but they don't know how important their library is to the client application. in your SQL example, if the application's whole purpose is to track inventory using that database, then yeah, SQLException is probably unrecoverable. but if the database is only needed for some ancillary functionality, the application writer probably just wants to tell the user "hey, this feature isn't available right now" and let them keep on using the rest of the program. maybe I'm missing some context here? I'm primarily a c++ dev, and I don't know much about SQL either. in my project, a crash is only acceptable if we are out of memory or if data corruption is imminent.