Ticket #4563 (closed defect: fixed)
Opened 5 years ago
Last modified 5 years ago
Scheduler ambiguous SQL query with certain custom recording rules
|Reported by:||taco_mel@…||Owned by:||janne|
|Severity:||medium||Keywords:||mythbackend scheduler power search|
I had occasion to write a custom "power search" query that includes a table containing a column called 'recordid', and this makes the 'recordid' of the resulting query ambiguous. Here's what was run within MySQL:
INSERT INTO recordmatch (recordid, chanid, starttime, manualid) SELECT record.recordid, program.chanid, program.starttime, IF(search = 5, recordid, 0) FROM (record, program INNER JOIN channel ON channel.chanid = program.chanid)...
A patch for scheduler.cpp is attached to qualify that with the appropriate table name.
comment:1 Changed 5 years ago by janne
- Owner changed from ijr to janne
- Status changed from new to accepted
- Milestone changed from unknown to 0.21
comment:2 Changed 5 years ago by janne
- Status changed from accepted to closed
- Resolution set to fixed