Discussions
Categories
- 384.5K All Categories
- 2.5K Data
- 551 Big Data Appliance
- 1.9K Data Science
- 451.3K Databases
- 222.1K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 32 Multilingual Engine
- 561 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 561 SQLcl
- 4K SQL Developer Data Modeler
- 187.4K SQL & PL/SQL
- 21.4K SQL Developer
- 296.8K Development
- Application Development
- 18 Developer Projects
- 140 Programming Languages
- 293.5K Development Tools
- 112 DevOps
- 3.1K QA/Testing
- 646.2K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 186 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 21 Java Essentials
- 164 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 206 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 525 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 178 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 236 Portuguese
Triggers
752637
Member Posts: 27
i have multiple schemas with copies of the same trigger in each of them.
I want to find out, during the run time of a trigger in PL/SQL, which schema is the trigger triggered from?
I want to find out, during the run time of a trigger in PL/SQL, which schema is the trigger triggered from?
Tagged:
Best Answer
-
USER function
or
http://asktom.oracle.com/pls/apex/f?p=100:11:0::::P11_QUESTION_ID:1529405950004
Answers
-
USER function
or
http://asktom.oracle.com/pls/apex/f?p=100:11:0::::P11_QUESTION_ID:1529405950004 -
Hi,
The best way of refering objects is as schema.object to avoid any such confusion.
But you can always execute below query to know the current schema/user
select user from dual
This discussion has been closed.