2013-02-13, 06:35 PM
Braklet Wrote:I just took a closer look at npvr.db3 using SQLite Maestro. The output attenuation that kept me from seeing any imported Unique ID data has to do with the fact that the SCHEDULED_RECORDINGS.event_details column shows up typed as varchar(50), even though it ends up longer than that. I tried changing the definition to varchar(500) and was able to see all the data.This is just a SQLite Maestro display problem. The data is all there.
Quote:This reveals another issue: the recordings import preserves all the event strings, so that recording title, subtitle etc. show up as expected. But no corresponding rows are created in the EPG_EVENT table and the embedded event OID is left 0. So as it stands, NPVR can't detect imported duplicates.NextPVR doesn't need an entry in EPG_EVENT, since it stores a cached copy of the EPG_EVENT in the recording.
In the logs, you should see a "UpdateRecurringRecording" message for your recording, and just you should see a pile of lines saying "- Already has completed episode : xxxxxxxx", where these have come from the EPG_EVENT cached in your recordings.