|
Okay, it looks like I can't just use the new DB functionality since it's inherently tied to transactions, which means using it would result in the same vacuuming error that I fixed recently. So for now I would have to create a plugin-specific connection for normal operations (what the current fallback is doing) and probably duplicate the copying behaviour for the cases that are failing on Chromebooks.
|