mykle wrote:
I exported a WP database that had a MySQL View defined in it -- just a useful join of the taxonomy tables with the post tables, which we use for debugging and analysis. Not a real table at all.
However, the plugin (v0.4.2) exported that view as a real table -- a monstrously large one.
The import of that SQL file eventually failed due to unresolved references. But even if the import had not failed, this would be a bug. The plugin should either simply ignore Views, or else detect them & produce the SQL to recreate them. It should't export n*n-large tables of redundant data. I can't use WP Migrate DB on this project anymore, and am back to editing SQL dumps with Perl for now.
BTW, I love the plugin overall and use it often. This is the first time it's ever failed me. Thanks very much for your contributions to WPland.
http://wordpress.org/support/topic/bogusindigestible-export-if-views-exist?replies=1#post-3288888
mykle wrote:
I exported a WP database that had a MySQL View defined in it -- just a useful join of the taxonomy tables with the post tables, which we use for debugging and analysis. Not a real table at all.
However, the plugin (v0.4.2) exported that view as a real table -- a monstrously large one.
The import of that SQL file eventually failed due to unresolved references. But even if the import had not failed, this would be a bug. The plugin should either simply ignore Views, or else detect them & produce the SQL to recreate them. It should't export n*n-large tables of redundant data. I can't use WP Migrate DB on this project anymore, and am back to editing SQL dumps with Perl for now.
BTW, I love the plugin overall and use it often. This is the first time it's ever failed me. Thanks very much for your contributions to WPland.
http://wordpress.org/support/topic/bogusindigestible-export-if-views-exist?replies=1#post-3288888