I forgot to mention: my code (and the patch above) is currently on version 17.2.5
Thinking about the matter, I find that this piece of code is obviousely bogus: > ORDER BY Job.JobId DESC, Job.JobTDate DESC LIMIT 1 Job.JobId is primary key (always distinct), so the second sort on Job.JobTDate is without effect. I might suppose that the original author mistakenly reversed the sort clause. Writing it as > ORDER BY Job.JobTDate DESC, Job.JobId DESC LIMIT 1 would give some logical sense. I would suggest that this gets changed in the master. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
