As I understand it, what you want to achieve is to restrict end user to access database only through one specific application, such as Forms, they are not allowed to enter database using anything else.
How about defining a log on trigger to act as gate keeper?
No, restriction only on DDL is far from enough.
What if a developer deletes some rows of a table via TOAD which relies on the application to enforce the consistency to another table based on certain business rule?
What if a power user intends to select the content of a table via SQL*Plus
which are accessed in application only by another business user in another department?
最初由 lazyoracle 发布
[B]As I understand it, what you want to achieve is to restrict end user to access database only through one specific application, such as Forms, they are not allowed to enter database using anything else.
How about defining a log on trigger to act as gate keeper? [/B]
能不能说得详细点?怎么as gate keeper