| How to exclude entity transactions from logging [message #1758045] |
Wed, 22 March 2017 20:11  |
Eclipse User |
|
|
|
|
I am asking if there is a way using SessionCustomizer or other, to exclude specific entity classes from logging ANY CRUD operations when normal sql logging is enabled. It would be "nice" to still see exceptions if/when they occur, but at a minimum to exclude INSERT and UPDATE statements, along with their bind data.
|
|
|
|
| Re: How to exclude entity transactions from logging [message #1758332 is a reply to message #1758324] |
Mon, 27 March 2017 13:38  |
| Eclipse User |
|
|
|
|
Completely agree. But what I "need" is some "better" examples of writing such a logger. I am "pretty" well versed in working with class descriptors and such, but I am just not "seeing" how to decide whether to log a statement or not. What I am expecting, is that I would like to write something where I can "detect" what is attempting to be logged. If I want that class logged, just pass it through, else block it by NOT passing it through. If I could get the "right" concept started, I could finish it to completion.
|
|
|
Powered by
FUDForum. Page generated in 0.04401 seconds
Home