zap2it vs. SchedulesDirect program ID format

[Braklet]

Has anyone else who tries to avoid repeats noticed that GB-PVR is mistakenly re-recording episodes after the SchedulesDirect transition?

Checking the database, I find that the new SD series IDs have two prepended zeroes which apparently throws off our repeat detection.

Thus far I've dealt with the situation by either deleting known repeat pending recordings, or hand-editing the associated program IDs. But there must be a better way of doing this.

Here's some discussion from the SD side:

http://forums.schedulesdirect.org/viewto...p?f=8&t=41

[-Oz-]

That is the new standard from TMS. Sooner or later all the EPG programs will have that.

[Braklet]

That is the new standard from TMS. Sooner or later all the EPG programs will have that.

If it is a new standard, is there any chance of a GB-PVR database fix? I can continue hand editing but I would expect a lot of messed up DBs if everybody resorted to it.

[sub]

I was only told about this change after the 1.0.16 release was out. It would sort itself out after while, so I wasnt too concerned about making a release to fix the existing program IDs in the database.

You want to, you can execute something like the following commands to correct it:

Code:

UPDATE PROGRAMME SET unique_identifier=SUBSTR(unique_identifier, 1, 2) || '00' || SUBSTR(unique_identifier, 3, length(unique_identifier)-3) WHERE length(unique_identifier) = 12;

I havnt tested this, so you'll probably want to backup your database first.

[Braklet]

Code:

UPDATE PROGRAMME SET unique_identifier=SUBSTR(unique_identifier, 1, 2) || '00' || SUBSTR(unique_identifier, 3, length(unique_identifier)-3) WHERE length(unique_identifier) = 12;

Thanks for the SQL. I'll look into some conversion techniques with SQLMaestro.