PS:
Serilog sink for PosgtresSQL: https://github.com/b00ted/serilog-sinks-
postgresql
--
Ticket URL: <https://code.djangoproject.com/ticket/34152>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_docs: 0 => 1
* needs_tests: 0 => 1
* easy: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/34152#comment:1>
* owner: nobody => alireza0sfr
--
Ticket URL: <https://code.djangoproject.com/ticket/34152#comment:2>
* status: assigned => closed
* needs_docs: 1 => 0
* resolution: => wontfix
* needs_tests: 1 => 0
* easy: 1 => 0
Comment:
Thanks for this ticket, however it's already covered by 3rd party
packages, e.g. `django-db-logger`. I'm not sure how using `serilog` is
different because I've never used it (as probably most Python developers).
Please first start a discussion on the DevelopersMailingList, where you'll
reach a wider audience and see what other think, and
[https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
features/#requesting-features follow the guidelines with regards to
requesting features]:
> ''"Describe clearly and concisely what the missing feature is and how
you’d like to see it implemented."''
--
Ticket URL: <https://code.djangoproject.com/ticket/34152#comment:3>
Comment (by Mohamed El-Kalioby):
You can use django-model-trackwr which allows you to know how and when a
change happened. Also, it allows you to revert to a previous version of
the object.
--
Ticket URL: <https://code.djangoproject.com/ticket/34152#comment:4>