4 ms·
Sure, but it's got to be better than the error you get from JDBC, which will be 200 lines long and not bother to include the SQL being executed, nor the usernam
by gaius 13y ago
Sure, but it's got to be better than the error you get from JDBC, which will be 200 lines long and not bother to include the SQL being executed, nor the username nor the database, making it utterly useless to anyone.
- dspillett 13y agoI'm not questioning the feature as a diagnostics tool, but the post I replied to seemed to be suggesting giving the error details out fairly directly to the user which is not good security practise (IMO). That 200 line JDBC error should not be going out to the end-user at all either, especially not if it did include the SQL being executed or worse still the db/authentication details (db name, user name).
- masklinn 13y ago> the post I replied to seemed to be suggesting giving the error details out fairly directly to the user I can't fathom how you'd come to such a conclusion from: > translate error information back into your application domain and generate logging and error messages which make sense to developers & end users. which describes more or less the opposite of "giving the error details out fairly directly".