[mythtv-commits] Ticket #4812: mythweather tables assume innodb is configured for mysql
MythTV
mythtv at cvs.mythtv.org
Sun Mar 2 14:09:28 UTC 2008
#4812: mythweather tables assume innodb is configured for mysql
---------------------------------+------------------------------------------
Reporter: rbonafied at gmail.com | Owner: stuartm
Type: defect | Status: new
Priority: minor | Milestone: 0.21
Component: mythweather | Version: 0.21-fixes
Severity: medium | Mlocked: 0
---------------------------------+------------------------------------------
I recently upgraded my friend's system to the 0.21-fixes (16181) branch
from an older svn revision. After confirming the myth schema upgrades
were complete, I started the backend and launched mythweb. Mythweb
errored out with a bunch of messages of 'missing weatherscreens' table.
[[BR]][[BR]]
Upon further investigation, it appeared that mysql had the tables in it's
catelog, but selecting from them returned 'table weatherscreens' does not
exist. Additionally, mysqlrepair showed them in the catelog but with
errors that the table didn't exist.[[BR]][[BR]]
After several tries at removing the phantom tables, I succeeded by moving
the flat files out of the mysql directory that represented the tables.
Then I removed the settings entry for mythweather in the hopes that myth
would see the tables missing and re-create them the right way. Myth did
re-create the tables, however they were still phantom
(unusable).[[BR]][[BR]]
Looking at the table creation code in mythweather/dbcheck.cpp I saw it
made a hardcoded reference to TYPE=InnoDB . Once I removed this
reference, the tables were created and usable.[[BR]]My mysql server is not
configured to use InnoDB.
--
Ticket URL: <http://svn.mythtv.org/trac/ticket/4812>
MythTV <http://svn.mythtv.org/trac>
MythTV
More information about the mythtv-commits
mailing list