Discussions
Categories
- 197K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.8K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 555 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.3K Development
- 17 Developer Projects
- 139 Programming Languages
- 293K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 158 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 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
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 468 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
can some one explain me this
Answers
-
i used different alphabet but its showing error..
can we use any other alphabet other than v ?
-
That's what i fear, the database doesn't know this APEX function or even your user hasn't the rights to use this function.
Try this
SELECT * FROM all_objects -- or dba_objects if you have access to this WHERE object_name = 'V';
If you don't have access to v then you can try to work without it:
:new.created_by := user;
That works without APEX.
regards
Kay -
:new.created_by := nvl(t('APP_USER'),user);
here i used "t" but its showing error as
Compilation failed, line 7 (12:33:48) The line numbers associated with compilation errors are relative to the first BEGIN statement. This only affects the compilation of database triggers.
PLS-00201: identifier 'T' must be declaredCompilation failed, line 7 (12:33:48) The line numbers associated with compilation errors are relative to the first BEGIN statement. This only affects the compilation of database triggers.
PL/SQL: Statement ignored
-
your database user who create your trigger doesn't see the function v or t or he isn't allowed to execute it.
Have a look at all_objects.
-
Amazing. You put random letters into your code, and Oracle doesn't automatically translate them into functions which do whatever it is you want them to do. Who would have guessed that?
-
Where did 't' come from? Error says there is no such thing as 't'.
What was wrong with v? What errors were you getting? What do you even want this trigger to achieve? And if you're feeling super helpful, what version of Oracle is this? What version of apex are you using?
-
KayK wrote: will this APEX function work on a pure database trigger and will it be accessible ? I'm coming from Forms 4.5 (20 years ago) and have only a little knowledge of APEX.
If the trigger or procedure is called from within an Apex application session, then yes the v functions will work just fine. If they're called from a regular session then they will return null.
-
2848515 wrote: i used different alphabet but its showing error.. can we use any other alphabet other than v ?
No. the "v" functions are specific to Apex application environment. You cannot just randomly pick any letter and expect it to work, unless you've specifically created functions (or have access to functions) with that name.
-
i just tried with other letters will they work or not ?
that's it...
-
No, random letters will not work unless you have a function named by that random letter.