Bug 187045 - Full CollectionScan fails: Specified key was too long error
Summary: Full CollectionScan fails: Specified key was too long error
Status: RESOLVED WORKSFORME
Alias: None
Product: amarok
Classification: Applications
Component: Collections/Local (show other bugs)
Version: 2.1-SVN
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-13 13:12 UTC by simon
Modified: 2009-03-16 17:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description simon 2009-03-13 13:12:01 UTC
Version:           2.1-SVN (using 4.2.64 (KDE 4.2.64 (KDE 4.3 >= 20090218)), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.26-tuxonice

hi,

amarok doesn't build my collection anymore with the following error.
As advised in the mysql forums http://forums.mysql.com/read.php?22,154827,155061#msg-155061 there shouldn't be a key created from a url field, rather the MD5 hash of it should be used.

this is a real showstopper as i just can have about 5% of my data imported into amarok.


amarok: BEGIN: void ScanManager::startFullScan()
amarok: BEGIN: void ScanManager::cleanTables()
amarok: END__: void ScanManager::cleanTables() - Took 0.0017s
amarok: BEGIN: XmlParseJob::XmlParseJob(ScanManager*, SqlCollection*)
amarok: BEGIN: void ProgressBarNG::setDescription(const QString&)
amarok: END__: void ProgressBarNG::setDescription(const QString&) - Took 0.00011s
amarok: BEGIN: void CompoundProgressBar::addProgressBar(ProgressBarNG*, QObject*)
amarok:        setting fixed height:  29  *  1  =  33
amarok:        p before:  QPoint(2,-34)
amarok:        p after:  QPoint(4,933)
amarok:        we now have  1  progress ops running
amarok: BEGIN: void ProgressBarNG::setDescription(const QString&)
amarok: END__: void ProgressBarNG::setDescription(const QString&) - Took 7.2e-05s
amarok: END__: void CompoundProgressBar::addProgressBar(ProgressBarNG*, QObject*) - Took 0.00086s
amarok: BEGIN: ProgressBarNG* ProgressBarNG::setAbortSlot(QObject*, const char*)
amarok:        Setting abort slot for  "Musik wird durchsucht"
amarok:        connecting to  1deleteLater()
amarok: END__: ProgressBarNG* ProgressBarNG::setAbortSlot(QObject*, const char*) - Took 0.00018s
amarok: END__: XmlParseJob::XmlParseJob(ScanManager*, SqlCollection*) - Took 0.0022s
amarok: BEGIN: virtual void XmlParseJob::run()
amarok: BEGIN: ScanResultProcessor::ScanResultProcessor(SqlCollection*)
amarok: END__: ScanResultProcessor::ScanResultProcessor(SqlCollection*) - Took 7.2e-05s
amarok:      Checking for batch file in  "/home/user/.kdelive/share/apps/amarok/amarokcollectionscanner_batchfullscan.xml"
amarok: BEGIN: bool ScanManager::readBatchFile(QString)
amarok:        splitData.size =  1
amarok: END__: bool ScanManager::readBatchFile(QString) - Took 0.3s
amarok: END__: void ScanManager::startFullScan() - Took 0.3s
amarok: BEGIN: void DatabaseUpdater::createTemporaryTables()
amarok:      [ERROR!] GREPME MySQLe query failed! Specified key was too long; max key length is 3072 bytes  on  "CREATE UNIQUE INDEX urls_id_rpath_temp ON urls_temp(deviceid, rpath);"
amarok: END__: void DatabaseUpdater::createTemporaryTables() - Took 0.022s
amarok: BEGIN: void CollectionSetup::writeConfig()
amarok: BEGIN: QStringList MountPointManager::collectionFolders()
amarok: END__: QStringList MountPointManager::collectionFolders() - Took 0.00066s
amarok: END__: void CollectionSetup::writeConfig() - Took 0.0021s
amarok(26599) Amarok2ConfigDialog::~Amarok2ConfigDialog: "  "
amarok: BEGIN: virtual OSDWidget::~OSDWidget()
amarok: END__: virtual OSDWidget::~OSDWidget() - Took 0.00023s
Comment 1 simon 2009-03-16 17:05:43 UTC
ok, works again with latest svn