Store saved variable TranscriptIgnore separate from TranscriptDB

[emmericp]

Describe the problem

A large log in TranscriptDB will effectively corrupt the entire saved variables file, causing you to lose both TranscriptDB and TranscriptIgnore.

If one of these two was a per-character var that would avoid the problem, but having either of these per character would be annoying. So my suggestion would be to add an extra empty addon that is just used to export/store TranscriptDB.

What steps will reproduce the problem?

1. Save something in TranscriptIgnore
2. Log a lot
3. Reload UI

[funkydude]

The problem with this is that there is no solution with 0 negatives.
This issue keeps cropping up essentially every time a new raid enters a testing phase, and it's always a headscratcher of how to resolve it in a good way.

I've even thought about having multiple addons and spreading all the logs across them, but the issues include:

• Having to jump across addons would be hostile towards people trying to read the logs - the whole point the logs aren't compressed.
• It's not compatible with people wanting to use the Git repo directly.
• It's admittedly a hacky workaround.

While the first point wouldn't be valid for your suggestion of just splitting the options DB, the other 2 are.

I honestly do not understand why Blizzard cannot implement a solution for this. Even if they keep the hard limit of entries in a specific table, having separate tables (DB entries) should be safe from each other?

[Road-block]

You can have a combination of both.

1. Save TranscriptIgnore to account SV
2. Load TranscriptIgnore from account SV > fallback to copying it over from PerChar SV if PerChar SV has something and Account does not.
3. CopyTable TranscriptIgnore > PerChar SV on PLAYER_LOGOUT (or if that event follows the sv spool and thus would come after the corruption, pick another opportune time, like transcript start/stop)

The end result is that you have a backup of TranscriptIgnore in PerChar SV, but still a unified setting.