"Rating" in cached event details xml

[mvallevand]

I meant the sqlite ATTACH command that lets you use a second database.

Martin

[imilne]

I meant the sqlite ATTACH command that lets you use a second database.

Ah, right. Sorry. Long day (with too early a start to get up to watch the Grand Prix, compounded by the clocks going forward too )

Since sub isn't going to be using this, couldn't the same think be achieved by a left outer join on the attached db?

My db skills are pretty limited in this area, so I'll just take your word for it.

But wouldn't sub have to do _something_ with it, as he's the only one that could paint the colours in the guide?

Iain

[mvallevand]

I think that is the source of the bickering yesterday, I am still assuming sub is not going to be using any of this, so I didn't think we needed to spend a lot of time on supporting values in his table.

Martin

[imilne]

I was trying not to assume anything, but I was *hoping* he might humour us for some stuff, which is why I thought reducing what would be needed in EPG_EVENT to just one extra field might sit well with him.

As I said, ever the optimist

Iain

[zehd]

I think that is the source of the bickering yesterday, I am still assuming sub is not going to be using any of this, so I didn't think we needed to spend a lot of time on supporting values in his table.

Martin

I just didn't want to reinvent the wheel. But if Sub won't include it in his TV Guide, then we will need to make another plugin. (I say this with no affect). Though I'm pretty sure Ailbert is on his way. His Listings for GB_PVR was great.

Data wise.. I agree, a join would totally work.

Actually I have discovered how to go ahead and add columns to nPVR native tables... and so long as there isn't a name conflict with any thinking nPVR is doing.. storing 3rd part one to one data would work well... and generally, the database structure does not reduce columns, but only increases over time with development... so this would be backward compatible.

But then there is the issue of 'staying out' of sub's tables.. so to be safe... a join to an outside table would be best, I'm sure