Reply to thread

Message

<blockquote data-quote="dvdfreak" data-source="post: 229460" data-attributes="member: 21313">Hmmm, you're the second one to report time-out errors on the database.&nbsp; So I'm trying to figure out what could have changed to cause this apparant deadlock, since I did not change all that much between 1.0.14.0 and 1.0.15.0...Anyone else seeing these same timeout errors on the database?This is normal unfortunately since TV Scheduler knows nothing of that XML file.&nbsp; The TVE3 plugin registers the recorded program with TV Scheduler, so that's why it's shown in the overview, but apart from that TV Scheduler doesn't know there was also an XML file written by TVE3.Yes <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />&nbsp; I'll have a look.&nbsp; I guess a total refresh happens and I'd expect the first entry to be selected then, but it sounds like a random one is then selected.&nbsp; Would be best to simply clear the selected I guess.The TVE3 plugin does not look at the Keep setting right now I think, perhaps I should sync that setting as well, yes.TV Scheduler is going to evolve and do its own conflict management and handle the scheduling of recordings itself, and then as a result will also clean up older recordings according to the keep setting.&nbsp; Still future stuff though <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Sounds like a reasonable solution, yes.Good point.&nbsp; Perhaps it would be even better for me to automatically add the wildcard, to the front and back.&nbsp; So if you enter &quot;Cruise&quot; it would find &quot;Tom Cruise&quot; and also &quot;Tom Cruise (Some Guy)&quot;.</blockquote>

[QUOTE="dvdfreak, post: 229460, member: 21313"] Hmmm, you're the second one to report time-out errors on the database. So I'm trying to figure out what could have changed to cause this apparant deadlock, since I did not change all that much between 1.0.14.0 and 1.0.15.0... Anyone else seeing these same timeout errors on the database? This is normal unfortunately since TV Scheduler knows nothing of that XML file. The TVE3 plugin registers the recorded program with TV Scheduler, so that's why it's shown in the overview, but apart from that TV Scheduler doesn't know there was also an XML file written by TVE3. Yes :) I'll have a look. I guess a total refresh happens and I'd expect the first entry to be selected then, but it sounds like a random one is then selected. Would be best to simply clear the selected I guess. The TVE3 plugin does not look at the Keep setting right now I think, perhaps I should sync that setting as well, yes. TV Scheduler is going to evolve and do its own conflict management and handle the scheduling of recordings itself, and then as a result will also clean up older recordings according to the keep setting. Still future stuff though :) Sounds like a reasonable solution, yes. Good point. Perhaps it would be even better for me to automatically add the wildcard, to the front and back. So if you enter "Cruise" it would find "Tom Cruise" and also "Tom Cruise (Some Guy)". [/QUOTE]

Verification