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
I've been using the library to ingest data into a database that's already defined in the SQLAlchemy ORM. As a result, I can define the batch table from importing classes I've got stored elsewhere. The downside is that when I attach their metadata, logging is flooded with updates for every single table in the database.
It's probably not a priority so I thought I'd put this in discussion, but is it worth adapting some of the logging to mitigate some of this? Is some of this useful in a non-apparent way? Would multiple "info" logging levels perhaps be useful?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've been using the library to ingest data into a database that's already defined in the SQLAlchemy ORM. As a result, I can define the batch table from importing classes I've got stored elsewhere. The downside is that when I attach their metadata, logging is flooded with updates for every single table in the database.
Separately there's also logging for stuff that might not happen, like "creating table if it doesn't exist" even when it exists, and logging of
on_before_visible
even if it's not used.All in all, I've just found logging quite noisy.
It's probably not a priority so I thought I'd put this in discussion, but is it worth adapting some of the logging to mitigate some of this? Is some of this useful in a non-apparent way? Would multiple "info" logging levels perhaps be useful?
Beta Was this translation helpful? Give feedback.
All reactions