Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 808fcdf

Browse files
committed
Update documentation for customer reporter
1 parent 1819ca7 commit 808fcdf

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

docs/userguide/reporters.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -175,6 +175,16 @@ If you need to produce a colored text output from the custom reporter, then you
175175

176176
It is recommended to create the reporter type in the schema where utPLSQL is installed (by default it is the `UT3` schema). Note that before running the utPLSQL uninstall scripts, all custom reporters should be dropped (cf. [the installation documentation](install.md)). In particular, when upgrading to a newer version of utPLSQL, one has to drop the custom reporters and recreate them after the upgrade.
177177

178+
!!! note
179+
Please make sure that grants have been added and synonyms created for the custom reporter in order for reporter to be accessible the same way as other reporters.
180+
Assuming that reporter with name `customer_reporter` was created in schema `UT3`
181+
```sql
182+
grant execute on ut3.custom_reporter to public;
183+
create or replace public synonym custom_reporter for ut3.custom_reporter;
184+
```
185+
186+
187+
178188
!!! note
179189
It is possible, but cumbersome, to use another schema for storing the custom reporters. This requires to create a synonym for the base reporter type in the schema that is going to own the custom reporter, and to provide appropriate grants both to the owner of the custom reporter and to the user running the reporter. After upgrading or reinstalling utPLSQL, the extra privileges need to be recreated. This approach is not recommended.
180190

0 commit comments

Comments
 (0)