[mythtv-users] Importing recordings from 18.x into 20.x, lessons learned
stephen.boddy at btinternet.com
Thu Oct 19 00:49:11 UTC 2006
On Wednesday 18 October 2006 18:58, Michael T. Dean wrote:
> On 10/18/06 11:53, Stephen Boddy wrote:
> >Well, I'm glad that Ackster attempted this. For some odd reason, doing it
> >the "proper" way, allowing 0.20 to upgrade the DB from 0.18, I ended up
> > with a bunch of recordings that showed as 1 Jan 1970 in MyhWeb. These
> > recordings lack detail in the progstart/end fields. Following his tips
> > looks to have cured that little niggle.
> And do you see in your logs something about:
> Current Schema Version: 1095
> Newest Schema Version: 1160
> and then something about a failed upgrade every time you start
> mythbackend, mythfrontend, or mythtv-setup?
Nope, I show:
2006-10-18 16:48:45.623 Using runtime prefix = /usr
2006-10-18 16:48:45.778 New DB connection, total: 1
2006-10-18 16:48:45.829 Connected to database 'mythconverg' at host: localhost
2006-10-18 16:48:45.873 Current Schema Version: 1160
All upgraded and working.
Looking at your subsequent response to Ackster, I perhaps wasn't entirely
clear. The database was upgraded going from 0.18 to 0.20, and the table has
the progstart/end field. The strange bit was that something like 30% of my
recordings had no timestamp in progstart/end, while the other 70% did. This
meant that I had a large chunk of recordings that showed up in MythWeb as
being from 1970, as it obviously takes the airdate from progstart.
More information about the mythtv-users