Enable session specific logging

[martindsouza]

From @martindsouza on January 26, 2013 14:31

Ability to set the configuration specific to a session. Odds are use client identifier so APEX sessions can leverage it.

Copied from original issue: tmuth#4

[martindsouza]

From @tmuth on January 26, 2013 15:26

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.

[martindsouza]

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.

[martindsouza]

From @tmuth on January 28, 2013 15:47

Possibly add new flag to enable it, but not as a new logger_level. Similar to SCN. client_identifier, PL/SQL call.