[mythtv-users] Backend Migration/Consolidation

[Phil Roberts]

Have started investigation moving three backends to a new single backend and wish to retain the 'oldrecorded' information from each.

machine 1 - running myth 0.19.20060121-2  ( built from scratch - 6000+ recordings )
machine 2 - running myth 0.23 fixes ( mythbuntu )
machine 3 - running myth 0.25 fixes ( mythbuntu )

machine 4 - new environment myth 0.27 fixes

A mysqldump of oldrecorded from 0.23 and 0.25 results in dropping the database table before inserting the records.  That is not so difficult to resolve. ( remove the drop and ALTER instead of CREATE ) I think.

The ouput from 0.19 however has not only a different length 'programid' but most of the data after the 'category' is different than the 0.23 and 0.25 data.

Sample 0.19 data ( after 'category' )

'EP000324','EP0003240092',0,11966,'Channel 3',4,1,-3,0,0);
'EP364495','EP3644950081',0,12248,'Channel 13',1,1,-3,0,0);

while 0.23 and 0.25 look like:

'EP00951139','EP009511391090','',0,12,'WATL',1,0,-2,0,0,0),;
'EP01172991','EP011729911015','',0,13,'WAGA',1,0,-2,0,0,0);

A post here ( http://marc.info/?l=mythtv-users&m=137954347111880&w=2 ) mentions:

"The "forget"
logic has always been rather simple minded in that it relises and
subtitle and description to match."

Does this mean instead of trying to massage the old data into the new format one could simply delete ( or dummy populate ) every field after the subtitle and then populate 'oldrecorded' with the resulting date to migrate the info to the 0.27 backend ?

If not, the programid can be fixed by adding back the '00' which was stripped off to get schedules-direct xml data through the older software.  Not sure about what needs to happen to the other fields or if just adding the extra 'generic future' field ( current value 0 ) would work or not.

Phil

 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20140522/c3dbf6af/attachment.html>