I'm not sure when it happened (I've been using a build from back in
the 6600's), but when I CO'd and built 7259 I had a LOT of problems
running.
Basically, there were a whole load of columns that were supposed to be
added to card (DBox2 stuff), and a (basically) complete overhaul of
recorded (Adding basename, progstart, progend, timestretch and
recpriority) that caused me all kinds of problems.
I have managed to create them on my own DB, and found the following
little snippet VERY helpful in getting the recorded table to work:
UPDATE
recorded
SET
timestretch=0,
recpriority=0,
progstart=starttime,
progend=endtime,
basename=CONCAT(chanid,'_',DATE_FORMAT(starttime,'%Y%m%d%H%i%S'),'_',DATE_FORMAT(endtime,'%Y%m%d%H%i%S'),'.nuv')
WHERE
basename IS NULL
But every time either the frontend or backend starts they report:
2005-09-15 18:15:27.565 Setting Lock for Database Schema upgrade. If
you see a long pause here it means the Schema is already locked and is
being upgraded by another Myth process.
2005-09-15 18:15:27.638 New DB connection, total: 2
2005-09-15 18:15:37.659 Database Schema upgrade complete, unlocking.
That's every time.
Is there some DB update code missing?
--
Robert "Anaerin" Johnston
_______________________________________________
mythtv-dev mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
