You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when I set io.r2dbc.postgresql.QUERY=DEBUG, all the SQLs are in the log.
In our application we run several scheduled jobs which fetch very often from the database and this completely clogs the log.
This makes it very difficult to use the log, and we have only two equally bad alternatives: either search through completely clogged log and have too much information, or miss the information completely. Neither of the alternatives is good :)
User Story
As a developer,
I'd like to be able to configure Query/Param logging only at the level of single repositories, or even better at the level of single methods,
in order to be able to read the log efficiently.
The text was updated successfully, but these errors were encountered:
Background
Currently, when I set
io.r2dbc.postgresql.QUERY=DEBUG
, all the SQLs are in the log.In our application we run several scheduled jobs which fetch very often from the database and this completely clogs the log.
This makes it very difficult to use the log, and we have only two equally bad alternatives: either search through completely clogged log and have too much information, or miss the information completely. Neither of the alternatives is good :)
User Story
As a developer,
I'd like to be able to configure Query/Param logging only at the level of single repositories, or even better at the level of single methods,
in order to be able to read the log efficiently.
The text was updated successfully, but these errors were encountered: