@B4nan - could i please get a review on this ?

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.74%. Comparing base (fb4f889) to head (8a83bee).
Report is 24 commits behind head on master.

@@           Coverage Diff            @@
##           master    #6725    +/-   ##
========================================
  Coverage   99.74%   99.74%            
========================================
  Files         267      267            
  Lines       19755    19782    +27     
  Branches     4327     4679   +352     
========================================
+ Hits        19704    19731    +27     
  Misses         51       51            

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

thanks! so how is this supposed to work in production when logs are disabled? we need a way to log stuff to the file system specifically for the slow query logs (regardless of how the default logging is set up), your PR only adds the new logger namespace. you can already set up a file logger but that means all logs would go there, maybe we could allow having multiple loggers, and set them up with different namespaces. slow query logging could be enabled automatically this way (logging to a txt file only the slow queries, regardless of the debug ORM option)

Oh! Okay, so we want the slowQuery logs to appear even with the debug logs are disabled in the production. Got it. I can make those changes. Thanks for the feedback @B4nan .

I am not sure if this should be enabled by default, but to me this is a production feature, and in production you don't usually enable query logging, since it would slow down the app and pollute the app logs like crazy. I'd say the best way to support this would be allowing multiple loggers, they can log to different places (console, file, some 3rd party service), based on different settings (log levels). Alternatively, only the slow query logs could be treated as a special case, but the former approach sounds cleaner. I haven't been thinking much about this, also not sure how it works in other ORMs, let's first agree on how this could look like before spending more time with implementation.