Re: Newbie : Best data archive strategy

2018-06-12 Thread Mickael Barbo
>> >> 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@googlegro >> ups.com] *On B

Re: Newbie : Best data archive strategy

2018-06-12 Thread Gerardo Palazuelos Guerrero
; > *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 re

RE: Newbie : Best data archive strategy

2018-06-12 Thread Matthew Pava
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

Re: Newbie : Best data archive strategy

2018-06-12 Thread mickael . barbo
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

RE: Newbie : Best data archive strategy

2018-06-12 Thread Matthew Pava
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-users@googlegroups.com [mailto:django-users@goog