[mythtv-users] /find_orphans.py crashes mythbackend

[Udo van den Heuvel]

On 04-09-16 06:24, Hika van den Hoven wrote:
> To put it simple:
> Playing around with the database is Ok, it's your database. I do it a
> lot.
> But never ever blame anybody for your playing around! as you are doing
> in this thread!!!!

Why the exclamation marks?
Because I `played around` with the recorded table?
Did you look at that table? Or the wiki about that table?
https://www.mythtv.org/wiki/Recorded_table
Did you see what can go wrong when I 'play around'?
Please tell me.

> Once you step outside proscribed ways, in essence you're on your own.

The 'proscribed' way is flawed and failed to help me.

> We, ( I think I can speak for a lot of people on this thread) like to
> help you cleaning up your mess, but never ever blame others for your
> mess!

There is no mess.
You call it mess.
The only issue I see is that the backend asumes that every amount of
orphans to be deleted is small. It trusts the input too much.
A user on the system can simply gather a (largish) list of recordings
and ask the backend to delete these. The backend will, if the list is
large enough, stop working and crash.
Authentication is one thing but intrinsic safety (i.e.: stability)
should be first.

If these simple approaches are missed (i.e.: trust all input without
posting the limits for everyone to see) then we should expect certain
standards.
In these days one can know that input should not be trusted. (i.e.: Same
as in real life)
So the code should handle stuff accordingly.

I will just put this issue with the memory leak(s).
No popcorn yet, it is too early in the day.

Kind regards,
Udo