Is this project still maintained ?

[claytonedk]

Hi, I am looking for a logger library for my PL/SQL and APEX applications. I found this project and it is very interesting but last update was 7 years ago. Is it because it's mature or beause it's no longer updated / maintained / supported ? Is it works with newer APEX versions, like 20 to 24 ? Thank you.

[zaplatynski]

If you look at the 3.2.0 branch you see updates from about four years ago. Why that branch is not integrated into the master branch I could only guess. There is no release of that either.

[jgebal]

I don't think this project is actively maintained and up do date. Sorry.

[commi235]

While there is currently no active development this still works totally fine.
We use it for code instrumentation in nearly every project.
Haven't had any issues with it.

[jdc136]

@commi235 are you using 3.1.1 or the latest non-released branch, 3.2.0? I am setting up logger. I noticed running the install script (logger_install.sql) there are some errors, like View created with compilation errors or PLS-00049: bad bind variable 'NEW.PREF_TYPE' and similar. I decided to give Logger a try after reading this.

[commi235]

I use 3.1.1, the error during installation is a false positive.

[jdc136]

For anyone else who comes across this, there is a great video from Blaine Carter going over the installation and use of Logger.

[zaplatynski]

With branch 3.2.0 the directory layout was changed. It would be nice to get some insight why that was done. It makes it very hard to merge changes with the master. Maybe if I try to restore the directory structure on the 3.2.0 branch it would be possible to compare the sources.

We have some issues with the current master branch version because sometimes we have two log events at the same time which results in a check constrain voilation because the log events share the same id. Today it would make sense to replace such a numeric id with a UUID to avoid such obstacles.

[zaplatynski]

With branch 3.2.0 the directory layout was changed. It would be nice to get some insight why that was done. It makes it very hard to merge changes with the master. Maybe if I try to restore the directory structure on the 3.2.0 branch it would be possible to compare the sources.

We have some issues with the current master branch version because sometimes we have two log events at the same time which results in a check constrain voilation because the log events share the same id. Today it would make sense to replace such a numeric id with a UUID to avoid such obstacles.

This is very rare but happens. Overall it still works and is the best logging framework as far as I know. I know self developed logging frameworks in PL/SQL which still can not reach it.

[martindsouza]

All: Thanks for your interest in Logger. Unfortunately this code base is not maintained anymore.

At one point. I was working on some big changes for 3.2.0 including how Logger artifacts (i.e. the installer) was built. I don't recommend using it unless you're able to support the changes.

Regardless I (and I know a lot of others) use Logger in many projects and is very stable.

[jdc136]

@martindsouza thank you for the informed update!