[horde] horde-db-migrate

Claude Tompers claude.tompers at restena.lu
Thu Jun 7 11:52:32 UTC 2012


Hi,

When upgrading the databse from Horde 3 to 4 using th horde-db-migrate
script, I found two issues.

1) Blacklists/Whitelists that were saved before in the horde_prefs table
and are now in the ingo_lists table, have not been moved. So users were
complaining about having lost their lists.

2) The calendars were renamed. Before their main calendar had the
username as name, this changed to what appears to be a random string.
Calendar events though have not been 'moved', meaning the calendar_id
field in kronolith_events table has not been updated. During the upgrade
script I've seen passing a lot of messages like 'Ignoring user xyz ..'
for kronolith and I'm wondering if that has something to do with this
behaviour. If so, what are the conditions for an event not to be updated ?

king regards,
Claude

-- 
Claude Tompers
Ingénieur réseau et système
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.horde.org/archives/horde/attachments/20120607/ab257390/attachment.bin>


More information about the horde mailing list