Re: compression?

[Dave Hall]

You're probably half the storage space if you compressed the data, but certainly nothing like an order of magnitude reduction.

You can implement this yourself by registering a custom deserializer/serializer with the Django serialization framework, then using that with reversion. For example, subclass the existing JSON implemnetation to add compression.

Migrating your existing data will take a huge amount of time, however, so be aware.

On Thu, 23 Mar 2017 at 22:56 <na...@vida.com> wrote:

I know this was asked yet not implemented. Our database is around 65GB and half of it is reversion tables. I think it would save considerable amount of space if it the json was compressed. What are others' experience on that? It may be the case that we need to prune older than some date, but I believe we may have to keep all the history.

Thanks

Naci

--
You received this message because you are subscribed to the Google Groups "django-reversion discussion group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-reversi...@googlegroups.com.
To post to this group, send email to django-r...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-reversion.
For more options, visit https://groups.google.com/d/optout.