Part one of DB updates - Centralization

Part one of the DB updates - switching to using a centralized source
that uses a executor to parallelize.

I'd imagine the performance would be more arse than it already was if I
ran it now, which is why the next step is to change the save action to
use SwingWorker and be parallelized per conversation.

After that, set-up the UI for BatchTaskProgressPanel, and configure
those SwingWorkers to use it

0 files changed, 0 insertions, 0 deletions