DBRepair development

[ChuckPa]

There shouldn’t be any “unknown” library sections unless the section itself got deleted and there is a completely orphaned record floating in there.

I do remove them (or so I thought?) – which is what I’d like to verify with an actual known test case (your db)

[d2freak]

@ChuckPa

2. Expunge - Yes, this is basic initial cut of it.

   So the watch history is the next thing (if possible) to remove as part of expunge ? (I don’t know what’s in Plex’s cloud-sync versus what’s in the DB)
   I will look and grab it out of there if possible.
   I don’t know if there’s a way for me to see if a user has or doesn’t have access

How about letting us pick a user to remove the watch history for? Then we can manually delete the stale entries. The command could require typing the username out exactly.

[dane22]

@d2freak

How about letting us pick a user to remove the watch history for? Then we can manually delete the stale entries. The command could require typing the username out exactly.

Users in the PMS database is identified with an ID, and not their real name

To get the user behind the ID, only option is to query either the local database, that @ChuckPa tool has access to, or query plex.tv, that req. a user token, and the tool do not have access to that, only the server token

Could be wrong though, but doubt it

[RealJerk]

hehe I don’t think this program will ever be truly finished with all of our suggestions flowing in poor Chuck!

For removing stale users, maybe it can output an ordered list, time since last stream: oldest>newest

e.g.

1. shadow_falcon22 (NOT SHARED) > 1y5m 

2. lunarbyte > 3m

3. crimsonwave_7 > 17d

4. pixelnomad > 12d

5. echostorm99 > 3h

..

Enter user # to delete:

..

1 2 3

Users deleted:

1. shadow_falcon22 (NOT SHARED) > 1y5m
2. lunarbyte > 3m
3. crimsonwave_7 > 17d

@dane22 yep correct, the usernames + IDs are in the Plex DB that DBRepair is using, but the emails tied to those require usage of Plex API credentials - which are stored in preferences.xml

It should be possible for most people to use any kind of scrub feature based on usernames alone imo, but it shouldn’t be difficult to pull the Plex API from preferences.xml or is that crossing some kind of line?

[dane22]

@RealJerk

which are stored in preferences.xml

Above is the server token, and access only users currently shared with

When said, yes, could be used…

But does it belong to a database fix tool?

I’ll leave that for @ChuckPa to decide, but I do know he has a lot on his plate already!

[ChuckPa]

ALL:

I am really appreciating all this input.
It’s going to make DBRepair really great when it’s done.

For the moment, I do request folks focus on letting me know what’s not working.

I still have Auto, Import , and Replace to write.

while mentioning “Automatic”,

• Are there any objections to DBRepair examining if PMS is running
• Stop it if is
• Perform whatever work tasks are needed (of the different ‘workers’ I have)
• After reinstalling the updated Live db
  If PMS was running, restart it.

Stop/start is dependent on the DBRepair’s ability to start/stop
(what you see now “the ‘not available’ message cannot be present”)

As soon as we hit production release (a 26.xx.00) number (industry standard)
then opening up for the enhancements is welcomed.

TODAY has had a number of great little fixes come in.

I am going to HotFix version 0.1999.08 replace the binaries

I will post when it’s done and move the download links down to new post with updated Release notes.

It’s all very trivial (not enough to warrant a bump but enough to warrant getting out to everyone)

[ChuckPa]

ALL:

I have code, already built into DBRepair which shows you its configuration; he “Config” command.

It’s not presented as a menu option because I didn’t think it would be that desirable during normal use.

A user has asked me if I could make is a menu option.

Please let me know

• Make ‘Config’ a visible menu option
• Keep ‘Config’ off the menu but available

[ChuckPa]

@Insomnic_1

Thank you for confirming “Abuser error”

I was beginning to worry as it wasn’t making sense and neither Dane22 nor I could reproduce it.

To let you and everyone know,

Tomorrow I will be hot-fixing and bumping the version of DBRepair to .09

The OUTSTANDING feedback I got today, coupled with some real-world issues I never thought to look for, are going to get verified and then the code released.

I have analyzed what was sent and figured out what I need to add to DBRepair which is ready for final test and release. (it’s a weird, wild, and VERY IMPORTANT edge case to fix. DBRepair.sh would never solve it)

[RealJerk]

@ChuckPa

• Are there any objections to DBRepair examining if PMS is running
• Stop it if is
• Perform whatever work tasks are needed (of the different ‘workers’ I have)
• After reinstalling the updated Live db
  If PMS was running, restart it.

Allowing DBRepair to stop/start PMS would be ideal

A pet peeve of Plex’s Scheduled Tasks for optimising database/bundles/cache, you can never time it and it will often interrupt streams (large DB issues, maybe)

I plan on having DBRepair take over that job - Every X days, when Plex streams are 0, launch DBRepair

[StephenH]

@ChuckPa

Your feedback, Pro or Con, is invited

Gave current 0.1999.08 a good workout of all options on my M2 Mac Studio running Sequoia 15.7.9, nothing to report!

Found no errors no matter what I did.

Looking good @ChuckPa

[Insomnic_1]

@ChuckPa

while mentioning “Automatic”,

• Are there any objections to DBRepair examining if PMS is running
• Stop it if is
• Perform whatever work tasks are needed (of the different ‘workers’ I have)
• After reinstalling the updated Live db
  If PMS was running, restart it.

Stop/start is dependent on the DBRepair’s ability to start/stop
(what you see now “the ‘not available’ message cannot be present”)

I think that makes sense for having Auto as a simple “do the thing” function. That’s all I usually do anyways.

[ChuckPa]

@hottif

Please check your PM. Updated binary waiting for you.