Deletion recovery and version control for model instances in Django

[@ZFCaio]

The best Django channel

[@CloudWithDjango]

Thank you so much!!

[@francosbenitez]

Wow! Didn't know about this package. Amazing!

[@CloudWithDjango]

Yes, quite a great library for sure!

[@youbra4267]

Thanks ❤

[@CloudWithDjango]

My pleasure!

[@advanceprogramming225]

Thank you boss❤

[@CloudWithDjango]

My pleasure! :)

[@BishnuThapaMagar]

helpful ♥

[@CloudWithDjango]

Thank you!!

[@sebedebadong94]

Very helpful!
Can you do also with REST API?
And how do we like protect POST request from REST API on Production Enviroment setup.
Thank you!

[@CloudWithDjango]

Thank you!! I appreciate the suggestion!

[@AndreasThoma-y8k]

Can the revision work also if new fields are being added or being deleted?

[@CloudWithDjango]

Hi Andreas, thank you for your question. I'd suggest referring to the docs on this.

[@AndreasThoma-y8k]

Can other models have a Person foreign key from different revisions? (ex. A model has a Person foreign key of version 1.0.0 but another model has a Person foreign key of version 2.0.0)

[@CloudWithDjango]

Hi Andreas, thank you for your question. I'd suggest referring to the docs on this.

[@OperatorOperator]

What's the difference to django-auditlog?

[@CloudWithDjango]

Here, we specifically keep track of model versions and also can recover deleted objects

[@Omar_Bendary]

I think this package is going to be very heavy on the database cause it saves every version so we have alot of versions of database

[@CloudWithDjango]

We won't have lots of versions of the database, but yes lots of versions of the model instances. So, it would be best in production to have a lot of memory allocated if you want to keep track of your object instances.