[Tickets #7971] rampage table index error

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7971
------------------------------------------------------------------------------
  Ticket             | 7971
  Created By         | horde at smartsector.hu
  Summary            | rampage table index error
  Queue              | Kronolith
  Version            | 2.3
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


horde at smartsector.hu (2009-02-09 18:27) wrote:

the bug related with #7948

after we created the tables the 7948 errors gone away.

but when i add the 2. event to the calendar i recive the following error:
Fatal error: Uncaught exception 'Horde_Db_Exception' with message  
'QUERY FAILED: Duplicate entry '2' for key 2 INSERT INTO  
`rampage_objects` (object_name, type_id) VALUES  
('20090209234236.14139w80iit4xxss at 195.70.38.187', 2)' in  
/usr/share/php/Horde/Db/Adapter/Mysqli.php:299 Stack trace: #0  
/usr/share/php/Horde/Db/Adapter/Mysqli.php(324):  
Horde_Db_Adapter_Mysqli->execute('INSERT INTO `ra...', NULL, NULL) #1  
/usr/share/horde/content/lib/Objects/Manager.php(122):  
Horde_Db_Adapter_Mysqli->insert('INSERT INTO `ra...') #2  
/usr/share/horde/content/lib/Tagger.php(703):  
Content_Objects_Manager->ensureObjects('20090209234236....', 2) #3  
/usr/share/horde/content/lib/Tagger.php(186):  
Content_Tagger->_ensureObject(Array) #4  
/usr/share/horde/kronolith/lib/Tagger.php(122):  
Content_Tagger->removeTagFromObject(Array, Array) #5  
/usr/share/horde/kronolith/lib/Tagger.php(160):  
Kronolith_Tagger->untag('20090209234236....', Array, 'event') #6  
/usr/share/horde/kronolith/lib/Driver/sql.php(516):  
Kronolith_Tagger->replaceTags('20090209234236.... in  
/usr/share/php/Horde/Db/Adapter/Mysqli.php on line 299

the xml part abut this index:
    <index>
     <name>rampage_objects_type_object_name</name>
     <unique>true</unique>
     <field>
      <name>type_id</name>
      <sorting>ascending</sorting>
     </field>
     <field>
      <name>object_name</name>
      <sorting>ascending</sorting>
     </field>
    </index>

our solution is simply:
drop the unique index and it's work perfectly.