From 1dd077c8ccb2cba62803e0f12b707dfd562bae3a Mon Sep 17 00:00:00 2001 From: Markus Hohloch Date: Mon, 23 Jun 2025 11:52:43 +0200 Subject: [PATCH] Update Best Practices.md little typos --- docs/Best Practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Best Practices.md b/docs/Best Practices.md index f63cb33..7eb2015 100644 --- a/docs/Best Practices.md +++ b/docs/Best Practices.md @@ -117,7 +117,7 @@ Information logging will vary in each organization but should fall between the r - When did the process end ### Warning -`logger.log_warn[ing]` should be used for non-critical system level / business logic issues that are actionable. If it is a critical issue than an error should be raised and `logger.log_error` should be called. An example would be when a non-critical configuration item is missing. In this case a warning message should be logged stating that the configuration option was not set / mssing and the deafult value that the code is using in place. +`logger.log_warn[ing]` should be used for non-critical system level / business logic issues that are actionable. If it is a critical issue than an error should be raised and `logger.log_error` should be called. An example would be when a non-critical configuration item is missing. In this case a warning message should be logged stating that the configuration option was not set / missing and the default value that the code is using in place. ### Error `logger.log_error` should be used when a PL/SQL error has occurred. In most cases this is in an exception block. Regardless of any other configuration, `log_error` will store the callstack. Errors are considered actionalble items as an error has occurred and something (code, configuration, server down, etc) needs attention.