[kronolith] last git head update constraint violation

[Michael Rubinsky]

Quoting LALOT Dominique <dom.lalot at gmail.com>:

> Hello,
>
> As Horde 4 told me to migrate the database of kronolith, I did that:
>
> root at horde4:/var/horde#  horde/bin/db_migrate
> [  INFO  ] Migrating DB up.
> [  INFO  ] Current imp schema version: 2
> [  INFO  ] Ending imp schema version: 2
> [  INFO  ] Current ingo schema version: 5
> [  INFO  ] Ending ingo schema version: 5
> [  INFO  ] Current turba schema version: 5
> [  INFO  ] Ending turba schema version: 5
> [  INFO  ] Current kronolith schema version: 17
> 2011-02-23T17:57:31+01:00 INFO: Migrating to
> KronolithUpgradeCategoriesToTags (18)
> 2011-02-23T17:57:31+01:00 INFO: == 18 KronolithUpgradeCategoriesToTags:
> migrating =============================
> 2011-02-23T17:57:31+01:00 INFO: == 18 KronolithUpgradeCategoriesToTags:
> Migrating event categories. ===========
> SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry
> '▒v▒nements' for key 'rampage_tags_tag_name'
>
> What can I do?

Hm. I am unable to reproduce this no matter how many duplicate  
categories I add to the event table. The checks in Content_Tagger  
should catch this. A query is done to see if the tag name exists  
already in Content_Tagger::_checkTags(). You will need to find out why  
that query is not finding the existing entry.


mike

The Horde Project (www.horde.org)
mrubinsk at horde.org