Comments on: On Database Trigger and current schema issue http://oraclue.com/2010/01/06/on-database-triggers-and-current-schema-issue/ Oracle internals, debugging and undocumented features Thu, 27 Oct 2011 15:05:30 +0000 hourly 1 http://wordpress.com/ By: dario boring http://oraclue.com/2010/01/06/on-database-triggers-and-current-schema-issue/#comment-740 Wed, 27 Apr 2011 21:26:40 +0000 http://oraclue.com/?p=1123#comment-740 I though that database triggers did not applied to sysdba users, to avoid that dbas got locked out. It seemed a good idea…..

]]> By: Neil Johnson http://oraclue.com/2010/01/06/on-database-triggers-and-current-schema-issue/#comment-408 Sun, 17 Jan 2010 22:42:19 +0000 http://oraclue.com/?p=1123#comment-408 Hi,

I may be missing something here but is the point of the trigger to set the current schema for users other than TEST. The first new version you created would only fire for connections as TEST which would already have current_schema set correctly. Connections as an application user would not pick up the correct schema.

Therefore I think the second option you proposed is the correct option.

Interesting stuff.

Kind regards

]]> By: suresh http://oraclue.com/2010/01/06/on-database-triggers-and-current-schema-issue/#comment-401 Fri, 08 Jan 2010 19:21:22 +0000 http://oraclue.com/?p=1123#comment-401 it nice ..

]]>