Closed martindsouza closed 11 years ago
This is something a lot of people have asked for and a great addition. I'd like to benchmark the impact and potentially have the ability to completely disable it if there are negative performance implications.
Thanks, Tyler
On Jan 26, 2013, at 9:31 AM, giffyd notifications@github.com wrote:
Ability to set the configuration specific to a session. Odds are use client identifier so APEX sessions can leverage it.
— Reply to this email directly or view it on GitHub.
One idea I have is to create another table to store the sessions that you want logged. What it could look like is client_identifier, level, expiry_date. In the ok_to_log we can also reference this table. Since function result_cache is enabled it could have a minimal impact on performance provided not too many changes are made to the client_id table.
Possibly add new flag to enable it, but not as a new logger_level. Similar to SCN. client_identifier, PL/SQL call.
This issue was moved to OraOpenSource/Logger#4
Ability to set the configuration specific to a session. Odds are use client identifier so APEX sessions can leverage it.