[mythtv] [mythtv-commits] Ticket #7373: Table 'mythconverg.weatherdatalayout' doesn't exist
Fa
fayoeu at gmail.com
Tue Oct 20 07:16:48 UTC 2009
On Mon, Oct 19, 2009 at 11:43 PM, Michael T. Dean
<mtdean at thirdcontact.com>wrote:
> On 10/20/2009 02:14 AM, MythTV wrote:
>
>> #7373: Table 'mythconverg.weatherdatalayout' doesn't exist
>>
>>
>> Comment(by fayoeu@…):
>>
>> {{{
>> *************************** 5. row ***************************
>> Engine: InnoDB
>> Support: YES
>> Comment: Supports transactions, row-level locking, and foreign keys
>> Transactions: YES
>> XA: YES
>> Savepoints: YES
>> }}}
>>
>>
>>
>
> In that case, I need to know exactly how you did your upgrade, because you
> have a WeatherDBSchemaVer, but you have no weather tables.
>
I just remembered what happened now. Awhile back when I upgraded from one
of the fedora to another fedora version, mysql was upgraded and it had some
problems with a table. The table was probably related to mythweather and I
nuked that table and never used mythweather since then. So I think the
problem existed for a long time and not related to the myth upgrade. I
think you can close the ticket, it probably has nothig todo with upgrading
from 0.21 to 0.22...
>
> Is this the same host that ran MythTV 0.21 or did you move to a different
> host when you upgraded? Is the MySQL server the same MySQL server you used?
> Did you upgrade MySQL server when you upgraded MythTV? Did you back up
> your database? Did you do a restore? Was it a full restore (recommended)
> or a partial restore (not recommended)? How did you perform the restore?
> Basically, please let us know of any thing that may have happened that may
> have resulted in your losing the weather tables (as there is no code
> whatsoever in Myth that will remove them).
>
> Mike
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-dev/attachments/20091020/e023b7c7/attachment.htm>
More information about the mythtv-dev
mailing list