Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.8K Databases
- 221.5K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 477 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.8K SQL & PL/SQL
- 21.2K SQL Developer
- 295.3K Development
- 17 Developer Projects
- 138 Programming Languages
- 292K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 27 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 390 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1K Español
- 1.9K Japanese
- 230 Portuguese
How to export view with instead of trigger

Hi,
is there an easy way to export view together with instead of trigger created on the same view?
For example, if you create view and instead of trigger like this:
-- viewcreate or replace view v_dummy as select 1 a from dual;-- instead of triggercreate or replace trigger v_dummy_ioiu instead of insert or update on v_dummy referencing new as new old as old for each rowbegin null;end;
If you go to the export option (right click on View > Export) with this properties:
you will get only view code (create or replace view...). If you select option Dependents you'll get all depended object, but no trigger.
The code that I want is visible if you right click on view > Open > tab SQL:
Thanks in advance for help!
I'm using SQL Developer 17.4.0.355 on Mac.
Br,
Marko
Best Answer
-
The SQL page does more work, it also asks
union all
select dbms_metadata.GET_DDL ('TRIGGER', trigger_name ,owner ) from Dba_triggers where table_owner = :OWNER and table_name = :NAME
union all
which finds the trigger attached to the table (which in this case, is the view)
The Export feature is NOT making this call, which would get the trigger.
SELECT dbms_metadata.get_dependent_ddl('TRIGGER', 'V_DUMMY') from dual;
I'd call this a bug.
Answers
-
The SQL page does more work, it also asks
union all
select dbms_metadata.GET_DDL ('TRIGGER', trigger_name ,owner ) from Dba_triggers where table_owner = :OWNER and table_name = :NAME
union all
which finds the trigger attached to the table (which in this case, is the view)
The Export feature is NOT making this call, which would get the trigger.
SELECT dbms_metadata.get_dependent_ddl('TRIGGER', 'V_DUMMY') from dual;
I'd call this a bug.