CDKScheduler and case sensitivity

[LesMcQueen]

I've been using CDKScheduler for a short while now, and have found it invaluable for scheduling recordings that are over the horizon.

However, I notice that the search is case sensitive, which nearly caused me to miss shows due to the capitalisation (or lack of) in the EPG data.

What are the chances of seeing a case insensitive version?

I'd guess that the case of the search string and EPG data would need to be folded prior to the search taking place.

Hope you can help.

[Ton]

Hi Les,

What you could do, if you set the EPG to import over XMLTV, is to run a small util of mine called "EPGFilter".

It uses regular expressions to change information in the EPG. I use it to:
- Split title/subtitles for some shows (that are stored with: "Mythbusters: [episode name]" in the title and an empty subtitle
- Remove "overlapping" programs (some of the kids shows here have a two entrys like: "10:00 - 12:00 Childrens cartoons" and then the individual shows: "10:00 - 11:00 Postman Pat"; "11:00 - 12:00 The Tweenies".

It would require you to store the programs you want to record in yet another XML-file, but it would give you the results you wanted.

More information can be found in this thread: http://forums.nextpvr.com/showthread.php?t=11894

Regards,

[garetmax]

I haven't noticed any case-sensitive issues with CDK scheduler so I'm thinking it doesn't matter. I could be wrong though.

I'll bet KingArgyle knows.

[KingArgyle]

Yes, I believe it is case sensitive as it use the sql LIKE statement to find the matches. This in and of itself looks for an exact case sensitive match. The problem with changing this is that an SQL engine's built in function would need to be called to convert the strings it finds in the database to upper or lower case, and then make sure that CDK Scheduler passed the pattern in either upper or lower case as well.

It does look like it is doable in cross compatible database way, as SQL Server, SQLite, and most other databases seem to support the UPPER and LOWER ANSI string functions. (BTW, a very good comparision for cross database compatibility can be found here: http://en.wikipedia.org/wiki/Comparison_of_SQL_syntax)

I'm pretty much out of the loop on CDK dev, just don't have the time like I used too, and I'm sticking with 96, as it works, and my card isn't actively supported any more.

[garetmax]

So it sounds like it is case sensitive in the newer SQL versions but not in the older access v96 versions. I'm also running the v96 currently.

Is that correct?

[KingArgyle]

Yes, I believe that is correct. It depends on how Access treats the LIKE statement. Anyways, i always do case sensitive searches for recordings, so I really haven't noticed it one way or the other.

[garetmax]

Now that I've upgraded to SQL I'm seeing this issue.

As a simple change, I just changed my recordings setup in CDK to record by title partial instead of just by title.

[capone]

I just finally went to 98, and yes, w/ the "partial" set, CDK seems to work.

I know you don't have the time to fully support it, but unless I'm missing something, isn't this the only change it really needs to be up to date?

Yes, I believe it is case sensitive as it use the sql LIKE statement to find the matches. This in and of itself looks for an exact case sensitive match.

I'm pretty much out of the loop on CDK dev, just don't have the time like I used too, and I'm sticking with 96, as it works, and my card isn't actively supported any more.

[KingArgyle]

On my end it's more than just bring code down, updating, and recompiling. As I'm still on 96, I would need to upgrade to 98, and since my card isn't actively supported any more, there is little incentive for me to do so. With that said, the source is available for anybody to download and fix, and update. It's on sourceforge, and the reason we put it there was so that it wouldn't get lost if one of us wasn't able to work on it.

Again, this is a feature I still strongly think needs to be in the base GBPVR and not an add on. That is up to Sub to implement. I've offered the code for CDK Scheduler to him in the pass and he's politely declined using it. He has his own method he wants to use.

[capone]

I was just thinking that if you had the existing version make new recordings deafult to "record by title partial", it would be a "beta 97+" version you could post.

That would give a working version to your 97+ fanbase, and not require any real 97+ recoding.

NBD if you can't, and I know you don't have big inclination to do so. I just know there are quite a few fans of CDK, and this tweak would pretty much give it back to them.

Out of curisosity, is there was way to make "record by title partial" the default on the client side? Like something that can be added in <Configuration></Configuration>?

If that was the case, even just havign a note how to do this in wiki would be all people need to keep it up to date.

On my end it's more than just bring code down, updating, and recompiling. As I'm still on 96, I would need to upgrade to 98