SQL Dev 24.3 came with detailed error messages turned on, e.g.:
drop table nosuchtable purge
Error report -
ORA-00942: table or view does not exist
https://docs.oracle.com/error-help/db/ora-00942/00942. 00000 - "table or view%s does not exist"
*Cause: The specified table or view did not exist, or a synonym
pointed to a table or view that did not exist.
To find existing user tables and views, query the
ALL_TABLES and ALL_VIEWS data dictionary views. Certain
privileges may be required to access the table. If an
application returned this message, then the table that the
application tried to access did not exist in the database, or
the application did not have access to it.
*Action: Check each of the following
- The spelling of the table or view name is correct.
- The referenced table or view name does exist.
- The synonym points to an existing table or view.
which is absolutely terrible for experienced users.
We do know what common error messages mean, and if in doubt the oerr command has been available for years—including as a built-in command in SQL Dev (Classic)… Failing that, we've had the Error Messages guide from docs.oracle.com, not to mention MOS notes (for DBAs with a Support contract).
Therefore, having all that amount of information being thrown at us again and again whenever the simple message “ORA-00942: table or view does not exist” would suffice is more than unnecessary: it makes script output a lot harder to read, which makes it a painfully unwelcome change.
I understand that this was made as an attempt to help beginner users, among other features intended to make the 23ai Oracle Database more user-friendly. If I understand correctly, the latest versions of SQLcl, and of the SQL Dev extension for VSCode behave in the same way.
I wouldn't mind if that behavior could be turned off, as it can in 23ai SQL*Plus, using the SET ERRORDETAILS command (doc: link). Can you please add support for this command in all tools, including SQL Dev (Classic)?
Thanks in advance.
Best regards,