Akonadi backwards compatibility

[Clive Messer]

On Sunday 22 Feb 2009 18:09:31 Clive Messer wrote:
> On Sunday 22 Feb 2009 17:16:57 Rex Dieter wrote:

> I wish I had made notes but I didn't. I think the problem - akonadi's mysql
> instance refusing to start, was because of the discrepancy between the
> logfile size, set to 8M in '~/.local/share/akonadi/mysql.conf' after the
> upgrade, and the actual existing files on disk being larger. But take that
> with a pinch of salt - I was half awake at the time.

> > the change as introduced should only affect *new* akonadi db's, old ones
> > should be unaffected.

Rex,

It does affect existing setups.

The next time akonadi is re-started after the upgrade, 
'~/.local/share/akonadi/mysql.conf' is modified....

innodb_log_file_size=64M -> innodb_log_file_size=8M

mysql then refuses to start ......

InnoDB: Error: log file ./ib_logfile0 is of different size 0 67108864 bytes
InnoDB: than specified in the .cnf file 0 8388608 bytes!
090223 17:30:44 [ERROR] Default storage engine (InnoDB) is not available
090223 17:30:44 [ERROR] Aborting

Regards

Clive
-- 
Clive Messer <clive at vacuumtube.org.uk>