Bug 4076 - DBD::mysql::st execute failed: Unknown column 'me.name'
: DBD::mysql::st execute failed: Unknown column 'me.name'
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Database
: 6.5b1
: Other Linux (other)
: P2 critical (vote)
: ---
Assigned To: Dan Sully
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-09-09 23:36 UTC by Robin Rainton
Modified: 2008-09-15 14:39 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robin Rainton 2006-09-09 23:36:27 UTC
I just updated from 6.3.0 to 6.5b1`(mainly because I want firmware 58). There's clearly some database changes that should be performed that have not been. The following is seen in the log when startup is attempted:

2006-09-10 16:19:46.4826 DBD::mysql::st execute failed: Unknown column 'me.name' in 'field list' at /usr/local/slimserver/CPAN/DBIx/Class/Storage/DBI.pm line 771.
2006-09-10 16:19:46.4828 ERROR: Error executing 'SELECT me.name, me.value FROM metainformation me WHERE ( name = ? )': DBD::mysql::st execute failed: Unknown column 'me.name' in 'field list' at /usr/local/slimserver/CPAN/DBIx/Class/Storage/DBI.pm line 771.

2006-09-10 16:19:46.4829 ERROR: Backtrace follows:

2006-09-10 16:19:46.4831 Backtrace:

   frame 0: Slim::Schema::Storage::throw_exception (/usr/local/slimserver/CPAN/DBIx/Class/Storage/DBI.pm line 773)
   frame 1: DBIx::Class::Storage::DBI::_execute (/usr/local/slimserver/CPAN/DBIx/Class/Storage/DBI.pm line 826)
   frame 2: DBIx::Class::Storage::DBI::_select (/usr/local/slimserver/CPAN/DBIx/Class/Storage/DBI.pm line 852)
   frame 3: DBIx::Class::Storage::DBI::select_single (/usr/local/slimserver/Slim/Schema/Storage.pm line 55)
   frame 4: Slim::Schema::Storage::select_single (/usr/local/slimserver/CPAN/DBIx/Class/ResultSet.pm line 509)
   frame 5: DBIx::Class::ResultSet::single (/usr/local/slimserver/Slim/Schema.pm line 397)
   frame 6: Slim::Schema::single (/usr/local/slimserver/Slim/Music/Import.pm line 482)
   frame 7: Slim::Music::Import::stillScanning (/usr/local/slimserver/Slim/Control/Commands.pm line 1900)
   frame 8: Slim::Control::Commands::wipecacheCommand (/usr/local/slimserver/Slim/Control/Request.pm line 1463)
   frame 9: (eval) (/usr/local/slimserver/Slim/Control/Request.pm line 1463)
   frame 10: Slim::Control::Request::execute (/usr/local/slimserver/Slim/Control/Request.pm line 752)
   frame 11: Slim::Control::Request::executeRequest (/usr/local/slimserver/slimserver.pl line 925)
   frame 12: main::checkDataSource (/usr/local/slimserver/slimserver.pl line 411)
   frame 13: main::init (/usr/local/slimserver/slimserver.pl line 436)
   frame 14: main::main (/usr/local/slimserver/slimserver.pl line 1037)

2006-09-10 16:19:46.4832 DBD::mysql::st fetchrow_array failed: fetch() without execute() at /usr/local/slimserver/CPAN/DBIx/Class/Storage/DBI.pm line 853.
2006-09-10 16:19:46.4833 ERROR: Request: Error when trying to run function coderef [Slim::Control::Commands::wipecacheCommand]: [DBD::mysql::st fetchrow_array failed: fetch() without execute() at /usr/local/slimserver/CPAN/DBIx/Class/Storage/DBI.pm line 853.
]

2006-09-10 16:19:46.4835 Request: Command [wipecache] (Bad dispatch!)
Comment 1 Chris Owens 2006-09-10 15:32:01 UTC
See also bug 3878.

Robin, did you install from one of the full Slimserver packages, or are you running just from the tarball or what?
Comment 2 Dan Sully 2006-09-10 15:36:11 UTC
Also - were you running with MySQL in 6.3.0?
Comment 3 Robin Rainton 2006-09-10 16:02:50 UTC
I used 'rpm -U SlimServer_6.5_v2006-09-09.noarch.rpm'

This is with MySQL 4.1.6. Fedora Core 4.

To get round the problem I droped/recreated the schema with the scripts that ended up in here:

/usr/local/slimserver/SQL/mysql

schema_1_down.sql
schema_1_up.sql

Of course this meant a total rescan of the library was needed, etc, etc.
Comment 4 Dan Sully 2006-09-10 16:17:23 UTC
Ok, I was able to reproduce this with a 6.3.x database using MySQL (which was unsupported BTW).

Fixed in change 9577 - which forces a DB schema migration.