Hi Steve,
What a coincidence! I just added a new feature that allows plugin users to select a default database yesterday. I hope to release the next version before the end of this month. The new version supports csv uploads to other (remote) databases as well. Please let me know if this is what you are looking for when the version is available.
Best regards,
Peter
Hi Peter, I guess I won’t be sure without seeing it but it sounds promising.
I don’t use remote databases at all, everything that I do is local and in the local DB containing the wordpress data
The use case would be to be able to configure a database and a CSV import, take a backup and restore it to another wordpress installation and be able to use the CSV importer (and ideally data designer, but I can reverse engineer the table to get it back if needed)
I currently do this by editing WP_WPDA_CSV_UPLOADS table and changing the schema_name attribute. If this were possible to use [default database] or something instead of the “old_schema_name” then this would probably work 🙂
{“settings”:{“delimiter”:”,”,”date_format”:”%Y-%m-%d”,”has_header_columns”:”true”},”database”:{“schema_name”:”old_schema_name”,”table_name”:”blah”}
I look forward to trying it and will feed back when it is released
Thanks
Steve
Hi Steve,
When you import your csv file into a database table, you can export your table (including your data) from the data explorer and use the data explorer on another WordPress server to import your data. The plugin can do all the work for you.
To export a table including all data from a source server:
– Start the Data Explorer on the source server
– Find your table
– Click the Manage link
– In tab Actions click button EXPORT (select type = SQL)
– Download the export file
To import your table and data to a destination server:
– Start the Data Explorer on the destination server
– Click button Import data/Execute scripts
– Upload and execute the file create in the previous step
That should be all you need to do to copy a table from one WordPress server to another. Does this help?
Best regards,
Peter
Thanks, it does but in my case I tend to take the whole lot (wordpress DB and custom tables) as I have a plugin that interacts with the pages and the custom tables, so in order to keep my test and development copy consistent with production I restore the whole lot.
Most of what I am testing is the replacement of data in these custom tables with a new CSV (that starts, of course from excel – not my choice…) so checking the new imported data’s behaviour on copy of a production system is really useful, so using the same CSV import on the copy before I import it on production is key to what I am doing.
