Hi Mickael, It saves a copy of each record every time a record is changed. But it is saved in a separate table, so it doesn’t change your model’s table.
From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On Behalf Of mickael.ba...@gmail.com Sent: Tuesday, June 12, 2018 1:17 PM To: Django users Subject: Re: Newbie : Best data archive strategy Thanks Matthew for your response. I looked at Reversion. If I understand correctly what it did, it duplicate each transaction on internal database ? Le mardi 12 juin 2018 20:01:02 UTC+2, Matthew Pava a écrit : I think what you’re really looking for is an audit log. There are some Django packages available that do that automatically. You might find this one quite helpful, called Django Reversion: https://github.com/etianen/django-reversion From: django...@googlegroups.com<javascript:> [mailto:django...@googlegroups.com<javascript:>] On Behalf Of mickae...@gmail.com<javascript:> Sent: Tuesday, June 12, 2018 12:22 PM To: Django users Subject: Newbie : Best data archive strategy Hi, I'd like to archive some data. I came with this idea : class DataModel(models.Model): xxx class DataModelArchive(DataModel): pass The DataModelArchive database created has only "a pointer" to DataModel. I saw a post indicating that I'll have to first create an AbstractDataModel and inherit for it for both DataModelArchive and DataModel. Well, what is the "best way" to archive data using Django ? Thx for your attention Micka -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com<javascript:>. To post to this group, send email to djang...@googlegroups.com<javascript:>. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/ef59e00a-3354-44f5-9c99-5ca85885026e%40googlegroups.com<https://groups.google.com/d/msgid/django-users/ef59e00a-3354-44f5-9c99-5ca85885026e%40googlegroups.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com<mailto:django-users+unsubscr...@googlegroups.com>. To post to this group, send email to django-users@googlegroups.com<mailto:django-users@googlegroups.com>. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/86e18583-0376-43f2-8419-b557459b5ca7%40googlegroups.com<https://groups.google.com/d/msgid/django-users/86e18583-0376-43f2-8419-b557459b5ca7%40googlegroups.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/148f20f481e5409a833ea043f771cbda%40ISS1.ISS.LOCAL. For more options, visit https://groups.google.com/d/optout.
