This content has been marked as final. Show 2 replies
This issue has been reported before on this forum:
Unable to see the WHEN clause for a trigger.
The bug referenced in that thread is a regression from SQL Developer 3.1. and remains open. From the bug comments:
So the alternatives for working around this issue are:
With only minimal privileges, we query all_triggers to get only the package body (when-clause kept in a different column), whereas with SELECT_CATALOG_ROLE or DBA role we query dba_source that contains the full trigger source.
1. Keep multiple versions of SQL Developer installed, using 3.1 when you need to work with triggers.
2. Obtain additional privileges in order to avoid the regression in 3.2
Hope this helps,
SQL Developer Team
Thank you for the response Gary, and I apologize for the duplicate report. I will see if our dba team is willing to grant us this privilege. Either way, I await the next release of SQLD.