Important Announcement
This forum will be discontinued.
The creation of new topics is disabled.
Please open GitHub issues for the corresponding topics/products in the following Trivadis repositories:
- PL/SQL & SQL Coding Guidelines
- PL/SQL Cop Command Line
- PL/SQL Cop for SonarQube
- PL/SQL Cop for SQL Developer
- PL/SQL Cop Validators
- PL/SQL Analyzer
- PL/SQL Unwrapper
A lot of users have already a GitHub account and the management of the issues is better than in this forum. For example, closing a forum topic is never related to a product change. Closing a GitHub issue for an accepted bug means that the bug is fixed. This should simplify the work for all involved parties.
See this blog post for more information.
Thank you for your understanding.
Hi There.
I'm wondering if you have a recommended approach for logging PL/SQL code. I've used extensively in the past Apache LOG4J and LOG4NET, but I'm newbie regarding PL/SQL looging.
Any comments about these tools ?
http://log4plsql.sourceforge.net/
https://github.com/OraOpenSource/Logger
Thanks for your help
Diego.
Last version of log4plsql is from 2010-04-13 (see https://sourceforge.net/projects/log4plsql/files/ ).
Last version of Logger is from 2015-08-17 (see https://github.com/OraOpenSource/Logger/releases/tag/3.1.1 ). However there were some commits on the master branch since then. So it looks to be actively maintained. Therefore I'd suggest to go with Logger and file issues for bugs and enhancement requests when you find bugs or miss something.