Revise traces #40
Description
- revise what's currently logged on trace level and on debug and on info level - do we utilize these levels in the best way?
- dedicated (new) macros, which do nothing in release builds, should be used where-ever query strings or result values etc would be logged (
if cfg!(debug_assertions)should be helpful). - consider providing something like a SQL trace