Re: Newbie : Best data archive strategy

>> >> 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

; > *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

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

oups.com ] *On Behalf Of * > mickae...@gmail.com > *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

RE: Newbie : Best data archive strategy

@googlegroups.com] On Behalf Of mickael.ba...@gmail.com 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

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 inh