Deploying db changes between staging and production

  • Hi, is there any information stored by the plugin in the database that i need to migrate from staging to production together with the source code after upgrading the plugin?
    My goal is to generated diff script for deploying changes between staging/production environments, so that only needed changes will be deployed.
    Was wondering if changes to db can be detected with sql compare tools like Toad for MySQL?
    Made a little test:

    2) Exported tables of the plugin:
    khxpw_woocommerce_api_keys
    khxpw_woocommerce_attribute_taxonomies
    khxpw_woocommerce_downloadable_product_permissions
    khxpw_woocommerce_log
    khxpw_woocommerce_order_itemmeta
    khxpw_woocommerce_order_items
    khxpw_woocommerce_payment_tokenmeta
    khxpw_woocommerce_payment_tokens
    khxpw_woocommerce_sessions
    khxpw_woocommerce_shipping_zone_locations
    khxpw_woocommerce_shipping_zone_methods
    khxpw_woocommerce_shipping_zones
    khxpw_woocommerce_tax_rate_locations
    khxpw_woocommerce_tax_rates
    with sql dump.
    before and after upgrade from 3.0.7 to 3.1.1
    3) Imported the dumps to different local dbs
    4) compared them with Toad and couldn’t find the difference except at most 16 options in prefix_options table.
    It’s interesting, because woocommerce asked to update the db after upgrading the plugin.

    • This topic was modified 7 years, 3 months ago by warrior7089.
  • The topic ‘Deploying db changes between staging and production’ is closed to new replies.