From 36ec573b5a68bcbdee7a0c7ead6d5fe73093f041 Mon Sep 17 00:00:00 2001 From: Ian Carpenter Date: Fri, 9 Sep 2016 21:46:22 +0100 Subject: [PATCH] Issue 166 Fix the broken link to Set Level part of the documentation. --- docs/Installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Installation.md b/docs/Installation.md index a9a4f4d..4def012 100644 --- a/docs/Installation.md +++ b/docs/Installation.md @@ -56,7 +56,7 @@ create trigger, create procedure, create any context to existing_user; ##NO-OP Option for Production Environments -To make sure there is no fear of leaving debug statements in production code, Logger comes with a [NO-OP](http://en.wikipedia.org/wiki/NOP) (No Operation) installation file (logger_no_op.sql). This installs only a shell of the Logger package. All procedures are essentially NO-OPs. It does not even create the tables so there is absolutely no chance it is doing any logging. It is recommended that you leave the full version installed and simply [set the Logger level](Logger-API#procedure-set_level) to ERROR as the performance hit is exceptionally small. +To make sure there is no fear of leaving debug statements in production code, Logger comes with a [NO-OP](http://en.wikipedia.org/wiki/NOP) (No Operation) installation file (logger_no_op.sql). This installs only a shell of the Logger package. All procedures are essentially NO-OPs. It does not even create the tables so there is absolutely no chance it is doing any logging. It is recommended that you leave the full version installed and simply [set the Logger level](Logger API.md#procedure-set_level) to ERROR as the performance hit is exceptionally small. ##Objects The following database objects are installed with Logger: