There is a plugin called – Clean Options which promises to remove all unused entries from wp_options table. NOTE – that plugin hasn’t been updated for 2 years, you must do backup before using it. To remove all data manually You have to manually look into database for unused tables or rows and use the … Read more
Backup your Database and then use DROP statements to delete the tables manually via tools such as MySQL Workbench, or MySQL Query Bench. There are many alternatives you can use that provide GUIs for backuping up, restoring, and modifying DBs. Here’s the WordPress DB schema, do not delete any of these tables: http://codex.wordpress.org/Database_Description Aside from … Read more
I imported/exported between a single wordpress blog and a multisite wordpress without problems, many times. Personally on a multi-site wordpress I have a parent generic theme and each website has it’s own child theme with as few files as possible, mostly only html/css for custom post types. Security issues or big complicated options are most … Read more
Why would you need to log them? They’re defined in the code itself. Look at wp-admin/includes/upgrade.php. Every version that changes the DB has a function defined that does the job. The changes made for version 3.4 are defined in the upgrade_340() function. The changes made for 3.3 are defined in the upgrade_330() function. And so … Read more
Some plugins aggregate data over time without ever cleaning up. I remember Broken Link Checker did that back in the days when I was using it … The first step: Find all tables, count their size (data, indexes and total size). Sample query, DB_NAME is the constant from your wp-config.php: SELECT table_name, table_rows, concat(round(data_length/(1024*1024),2), ‘M’) … Read more
Ok, to resolve these issues, let’s implement the cascading upgrade process which will handle both use cases. First of all lets implement our plugin activation hook, which will be our entry point: // define current plugin version define( ‘WPSE8170_PLUGIN_VERSION’, ‘2.0.0’ ); // define our database table name define( ‘WPSE8170_DB_TABLE’, $GLOBALS[‘wpdb’]->prefix . ‘wpse8170_test_table’ ); add_action( ‘init’, … Read more
Figured it out upon examining my SQL file. It begins as SQL, and near the end changes to PHP. For some reason the download got messed up and the SQL export began outputting the PHP of the PHPmyAdmin page I was on! (not even just the client side HTML, it was spitting out server side … Read more
For the sake of the example, I’ll assume you to have copied the relevant Table to the WordPress DB, to have named it wp_my_xtra_table and it to contain 3 columns (id,num_val,str_val). function wpse106832_shortcode_demo( $atts ) { global $wpdb; extract( shortcode_atts( array( ‘id’ => 1 ), $atts ) ); $table_row = $wpdb->get_row( ‘SELECT * ‘ . … Read more
After an insert, the ID generated for the AUTO_INCREMENT column can be accessed with: $wpdb->insert_id Last sentence is just copyed and pasted form the codex.
I’m no SQL expert, but I think it would look something like this: SELECT * FROM mydatabase.wp_users INNER JOIN mydatabase.wp_usermeta ON (wp_users.ID = wp_usermeta.user_id) WHERE 1=1 AND wp_users.user_registered > ‘2014-03-15 00:00:00’ AND wp_users.user_registered < ‘2014-03-16 00:00:00’ AND ( (wp_usermeta.meta_key = ‘wp_capabilities’ AND CAST(wp_usermeta.meta_value AS CHAR) LIKE ‘%\”subscriber\”%’) ) ORDER BY user_registered ASC ;