Opened 19 years ago
Closed 19 years ago
#2051 closed defect (fixed)
DVB EIT update updates wrong airdate values
Reported by: | otto at kolsi dot fi | Owned by: | Stuart Auchterlonie |
---|---|---|---|
Priority: | minor | Milestone: | 0.20 |
Component: | mythtv | Version: | head |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
With SVN 10490, DVB-T, FC4, mysql-4.1.20-1.FC4.1:
When EIT info is updated to DB, airdate column gets skrewed. Below is one example of the update query where airdate column is updated with value '0'. When you update it like this, it actually gets value '2000'. Proper value to be used in update is '0000' which is used e.g. in DBEvent::UpdateDB(MSqlQuery &query, const DBEvent &match) in eit.cpp.
At least one place where this failure occurs is that same function. lairdate seems to be empty and match.airdate not -> match.airdate is used in update and it probably is not properly initialized, contains value '0' or something like that.
2006-07-13 20:42:07.255 MSqlQuery: UPDATE program SET title = 'Kesäillan valssi', subtitle = '', description = 'Perinteiset tanssiaiset Seinäjoen Tangomarkkinoilta. Solistivieraana Topi Sorsakoski ja säestävänä orkesterina Varjokuva. Mukana myös uusi SM-voittaja Nelinpeli. Juontajina Sari Tamminen ja Kyösti Mäkimattila, tangon askeleet opetta', category = 'Show/game Show', category_type = 'tvshow', starttime = '2006-07-13T21:00:00', endtime = '2006-07-13T21:46:49', closecaptioned = 0, subtitled = 1,stereo = 1, hdtv = 0, partnumber = 0, parttotal = 0, airdate = '0', originalairdate=NULL, listingsource = 1 WHERE chanid = 1033 AND starttime = '2006-07-13T21:00:00'
Attachments (1)
Change History (8)
comment:1 by , 19 years ago
Component: | dvb → mythtv |
---|---|
Milestone: | → 0.20 |
Owner: | changed from | to
comment:2 by , 19 years ago
Owner: | changed from | to
---|
comment:3 by , 19 years ago
comment:4 by , 19 years ago
Milestone: | 0.20 → 0.21 |
---|
If you can make a patch for this in the next couple days I'll apply it in time for 0.20.
comment:5 by , 19 years ago
Attached 'eit_airdate_fix.diff' patch fixes the airdate problem.
EIT data inserts to DB are okay, but when existing data is updated, match.airdate gets value '0' and when this is again updated back to DB -> airdate column gets value '2000'.
comment:6 by , 19 years ago
Milestone: | 0.21 → 0.20 |
---|---|
Status: | new → assigned |
Other symptoms: