Bugzilla – Bug 2840
Crash during scanning when using MySQL
Last modified: 2008-09-15 14:39:24 UTC
I also get the following error when I start a scan using MySQL: 2006-01-14 22:32:15.4961 directory entry: file:///L:/Music/Charvie/Alanis%20Mor issette/Jagged%20Little%20Pill/01%20All%20I%20Really%20Want.mp3 2006-01-14 22:32:15.8415 DBD::mysql::st execute failed: Field 'contributor' does n't have a default value at C:/Program Files/SlimServer_svn/server/Slim/DataStor es/DBI/DataModel.pm line 907. Can't insert new Slim::DataStores::DBI::Album: DBD::mysql::st execute failed: Fi eld 'contributor' doesn't have a default value at C:/Program Files/SlimServer_sv n/server/Slim/DataStores/DBI/DataModel.pm line 907. at C:/Program Files/SlimServer_svn/server/Slim/DataStores/DBI/DBIStore.pm line 1879 If I remove the NOT NULL attribute from the Album Contributor field in the file mysql/dbcreate.sql, the problem goes away. I'm not sure if a null contributor is valid? If it is valid, the NOT NULL attribute should be removed from the code. If its not valid (ie my tags are screwed), then SlimServer should catch the error condition instead of crashing.
Chris - do you still have this issue with the latest nightly builds? Thanks.
Hi Dan, Using svn r6921, I get the following error: 2006-04-13 17:38:00.1179 DBD::mysql::st execute failed: Field 'contributor' doesn't have a default value at C:/Program Files/SlimServer_svn/server/Slim/DataStores/DBI/DataModel.pm line 935. Can't insert new Slim::DataStores::DBI::Album: DBD::mysql::st execute failed: Field 'contributor' doesn't have a default value at C:/Program Files/SlimServer_svn/server/Slim/DataStores/DBI/DataModel.pm line 935. at C:/Program Files/SlimServer_svn/server/Slim/DataStores/DBI/DBIStore.pm line 1908 If I remove the NOT NULL attribute from the Album Contributor field, the problem goes away. This problem also occurs on the split-scanner branch. Cheers Chris
Thanks Chris - do you happen to have a corresponding audio file that is causing the crash? And if so, can you send it to me, or attach to the bug? Thanks.
I've checked in a schema update as change 6923
Looks good - I think this bug can be closed now. Thanks!! Chris