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
With this, developers can extend the LogEntry model to do whatever they want. We might even enable them to log to it from regular model saves via signals. The downside is this is a performance hit.
More thoughts:
Perhaps also allow for non-ORM records to be stored?
Perhaps a logging system or data store better for this many writes?
Could also work in a queueing system.
The text was updated successfully, but these errors were encountered:
+1 for DJADMIN2_LOGENTRY_MODEL
+1 for "Perhaps also allow for non-ORM records to be stored?"
I'm thinking.. when extending the LogEntry, sometimes I'll have to override things like ModelHistoryView, model_history.html, history.html. So, I'm just wondering if would be interesting to have some features as "extensions/plugins"? I mean, a package, so I can implement my needs and register on djangoadmin2.
It is something to consider, (worth to discuss), or am I just complicating things?
This is just a thought, but it would be similar to how the new Django auth.User model works:
With this, developers can extend the LogEntry model to do whatever they want. We might even enable them to log to it from regular model saves via signals. The downside is this is a performance hit.
More thoughts:
The text was updated successfully, but these errors were encountered: