Hi Ralph,
Glad to hear it!
The condensediffs savings should definitely be better in 2.5.x.
In 2.0, we condensed by de-duplicating diffs (if you uploaded 3 revisions
of a diff, but a diff for a file remained the same between revisions, we no
longer store multiple copies of it).
In 2.5.x, we move
Hi Christian,
Thanks, that was exactly the problem. After switching to InnoDB, the
upgrade to 2.5.2 completes, and I have a working install.
The one other change I had to make was the memcached backend name in
settings_local.py (CacheClass -> MemcacheCache).
I did notice a difference in the "co
On Monday, December 7, 2015 at 10:55:42 PM UTC-5, Stephen Gallagher wrote:
>
> Did you run this with the recent django-evolution 0.7.6 update? That
> specifically addresses some upgrade issues unique to MySQL.
>
Yes, I am using python-django-evolution-0.7.6-1.el7.noarch with your fix
from Dec 4t
Hi,
Looks like you have a mix of InnoDB and MyISAM tables. You're going to need
to update all tables in your database to use InnoDB (or configure MySQL to
use MyISAM by default, though InnoDB is preferable).
The workaround you have that results in the "attachment_histories" bit is
due to installi
Did you run this with the recent django-evolution 0.7.6 update? That
specifically addresses some upgrade issues unique to MySQL.
On Mon, Dec 7, 2015, 9:40 PM rfs wrote:
> Some additional information after further experimentation:
>
> * I tried upgrading from the same 1.7.27 database to 2.0.18. T
Some additional information after further experimentation:
* I tried upgrading from the same 1.7.27 database to 2.0.18. This worked
perfectly fine. I ran compressdiffs afterwards as suggested, that worked
too.
* I then tried upgrading from 2.0.18 to 2.5.2, but got the same "Can't
create table '
