• It would be nice if possible to have a generic “current local database” option on the database dropdown menus and saved in any WPDA job definitions – this would be used in the common example where work is being done on multiple databases on restored copies of wordpress.

    i.e. a production database is often backed up and restored to a non-prod server. All of the data work I do is local and on tables in the current schema used by wordpress, but WPDA seems to store a reference to the actual schema name in CSV import jobs and other places like data designer. This means I have to re-create these on the non-production system in order to test and replicate issues so it would be nice if there was a “current local database” placeholder that could be used in these case.

    I currently edit the wp_wpda_csv_uploads table to sort out the schema names for imports but haven’t managed to work out where the publisher keeps that information ??

    Thanks

    Steve

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Passionate Programmer Peter

    (@peterschulznl)

    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

    Thread Starter snyggapa

    (@snyggapa)

    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

    Plugin Author Passionate Programmer Peter

    (@peterschulznl)

    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

    Thread Starter snyggapa

    (@snyggapa)

    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.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘add generic “Local database” to database picker’ is closed to new replies.