Local Prefix vs. Flywheel Prefix

Workflow
1

Local creates database tables with “wp_” prefix. Flywheel creates random prefixes. I’m unable to use WP DB Migrate because the prefixes don’t match. Changing the prefix at Flywheel to match Local doesn’t actually “change” the prefix… it creates new empty tables, which requires a reinstall of WP. There’s no option to set or change prefix via Local, other than opening a database tool and manually changing the tables. It kind of defeats the purpose of the automated WP installs, if you have to reinstall (Flywheel) and/or manually change database prefixes (Local).

What’s the best way to approach all of this? Am I missing something? Is there a better way? Perhaps someone here has some tips to get Flywheel and Local working together seamlessly, with no database modifications?

2

Flywheel is generating those random prefixes for security purposes, so it looks like the best route would be to run a SQL script on the Local database to match the prefix on the Flywheel prefix.

There’s also a plugin available: https://wordpress.org/plugins/change-table-prefix/

I’m interested to see how the upcoming migration feature in Local will handle this. The Flywheel + Local experience would be flawless at that point.