Bugzilla – Bug 2881
db schema not being updated
Last modified: 2008-09-15 14:39:24 UTC
Running 6.5 with mysql, I SVN'd to r5880 and now get a crash on startup. It appears the db schema (running mysql) isn't being updated. Could this be because there were two version updates in succession (19 and 20)? Or... it looks like the schema, version 20 was only made to the 6.2 branch. The file server/SQL/mysql/sql.version contains the string '20', while server/SQL/mysql/Upgrades contains a 19.sql file, but no 20.sql. I recall running into a similar problem the last time the schema was changed. 2006-01-27 11:29:17.4500 Metadata database saving into: dbi:mysql:dbname=slimserver File 'C:\mysql\\share\charsets\?.conf' not found (Errcode: 2) Character set '#33' is not a compiled character set and is not specified in the 'C:\mysql\\share\charsets\Index' file 2006-01-27 11:29:17.5702 Connected to database dbi:mysql:dbname=slimserver 2006-01-27 11:29:17.6107 No upgrades found for database v. 19 2006-01-27 11:29:17.6120 DBI: Supressing periodic commit - no dirty items 2006-01-27 11:29:17.6136 loading types config file... 2006-01-27 11:29:19.4167 DBD::mysql::st execute failed: Unknown column 'customsearch' in 'field list' at C:\Program Files\SlimServer\server\lib/Class/DBI.pm line 1234. Slim::DataStores::DBI::Track can't SELECT id, url, content_type, title, titlesort, titlesearch, album, tracknum, timestamp, customsearch, filesize, tag, disc, thumb, remote, audio, audio_size, audio_offset, year, secs, cover, vbr_scale, bitrate, samplerate, samplesize, channels, block_alignment, endian, bpm, tagversion, drm, moodlogic_id, moodlogic_mixable, musicmagic_mixable, musicbrainz_id, playcount, lastplayed, lossless, lyrics, replay_gain, replay_peak FROM tracks WHERE url = ? : DBD::mysql::st execute failed: Unknown column 'customsearch' in 'field list' at C:\Program Files\SlimServer\server\lib/Class/DBI.pm line 1234. at C:/Program Files/SlimServer/server/Slim/DataStores/DBI/DBIStore.pm line 1157 2006-01-27 11:29:19.4669 forceCommit: syncing to the database.
Jim - just checked in a possible fix. Give that a try?
Yep, good to go. She's rescanning now. Thanks Dan.