0

Data-Loader: Duplicate entry issue

shen deshayne

December 01, 2011 00:20

None

Follow

I'm getting the following error (different performer on each server live/local) when I run the performers data-loader update. I delete the corresponding performer and get the same error. Same if I truncate the table. Any clue?

I believe it has to do with the lookup (fetchrow on data-loaders/performer.php line 86) being on the performer id, yet performerName needs to be unique.

 

PHP Fatal error: Uncaught exception 'Zend_Db_Statement_Mysqli_Exception' with message 'Mysqli statement execute error : Duplicate entry 'WWE - World Wrestling Entertainment' for key 'performerName'' in /usr/share/php/libzend-framework-php/Zend/Db/Statement/Mysqli.php:214

Stack trace:

#0 /usr/share/php/libzend-framework-php/Zend/Db/Statement.php(300): Zend_Db_Statement_Mysqli->_execute(Array)

#1 /usr/share/php/libzend-framework-php/Zend/Db/Adapter/Abstract.php(468): Zend_Db_Statement->execute(Array)

#2 /usr/share/php/libzend-framework-php/Zend/Db/Adapter/Abstract.php(546): Zend_Db_Adapter_Abstract->query('INSERT INTO `te...', Array)

#3 /usr/share/php/libzend-framework-php/Zend/Db/Table/Abstract.php(1052): Zend_Db_Adapter_Abstract->insert('tevoPerformers', Array)

#4 /home/vagrant/savefans/app-console/vendors/ticketevolution-php/library/TicketEvolution/Db/Table/Abstract.php(139): Zend_Db_Table_Abstract->insert(Array)

#5 /usr/share/php/libzend-framework-php/Zend/Db/Table/Row/Abstract.php(467): TicketEvolution_Db_Table_Abstract->i in /usr/share/php/libzend-framework-php/Zend/Db/Statement/Mysqli.php on line 214

• Facebook
• Twitter
• LinkedIn

4 comments

• 0
  
  J Cobb December 01, 2011 00:32

  I haven't really had a chance to dig into this one yet, but I do know that it stems from my dislike of the TEvo's insistance on NOT making venue & performer names unique.

  Because I truly believe they should be unique I have tried to enforce that in the data-loader tables. In my own version of the venues data-loader I even detect duplicate venue names and attempt to append the locality to the name because I think it is an extremely poor idea to have 18 "House of Blues" venues.

  At a minimum TEvo needs to NOT have two separate performers named "WWE - World Wrestling Entertainment" and deactivate one of them, which then reveals another issue I am working with TEvo to figure out. How & when to return items that are no longer inactive so that those of us caching the info can know that it is inactive. If you have any input or suggestions please let me know.

• 0
  
  shen deshayne December 28, 2011 01:19

  J, Here is how I updated my table to fix this issue:

   

  ALTER TABLE tevoPerformers DROP INDEX performerName;
  
  ALTER TABLE tevoPerformers ADD INDEX performerName (performerName);

   

  Maybe include it in the repo.

• 0
  
  J Cobb December 29, 2011 18:43

  Yeah, that works, but to me it isn't the desired solution. I've been pushing to have them make the performerName (and venueName) unique. They are still cleaning up some of the catalog which should be completed this week and then we can go back to working on making them actually be unique. Your solution should work in the interim.

• 0
  
  shen deshayne December 29, 2011 18:47

  Great, thanks.