To optimize the query, instead of use $wpdb->insert is possible to use $wpdb->query and use a single query that insert all the items. In fact, according to MySQL documentation: If you are inserting many rows from the same client at the same time, use INSERT statements with multiple VALUES lists to insert several rows at … Read more
Yes you can have more than one database, this type of set-up is for large traffic heavy sites and you would want to use something like http://wordpress.org/plugins/hyperdb/ . This is outside the scope of the vast majority of WordPress sites. You can manage a multitude of blogs from 1 db if you want using http://codex.wordpress.org/Create_A_Network. … Read more
First of all your query is wrong. The right query is $mypost = $wpdb->query($wpdb->prepare(“SELECT post_content FROM $wpdb->posts WHERE ID = %d”, 2)); Second the $wpdb->query will returns an integer value indicating the number of rows affected/selected. You can check here http://codex.wordpress.org/Class_Reference/wpdb#General_Syntax If you want generic result you can use $wpdb->get_results http://codex.wordpress.org/Class_Reference/wpdb#SELECT_Generic_Results $mypost = $wpdb->get_results($wpdb->prepare(“SELECT post_content … Read more
There’s some overlap, but each isn’t an abstraction of the previous, and there are definitely some things you don’t want to do outside of the API. Most things, actually! WP_Query is for retrieving posts and pages, it doesn’t update anything, and it doesn’t fetch data that isn’t a post or page. The higher level API … Read more
In typical use cases the performance cost of booting WordPress core for page load is significantly higher than querying for data. In other words it doesn’t quite matter, because it won’t be a bottleneck. You have to estimate: How close your data is to native WordPress concepts How much work (if any) it would be … Read more
While this is primarily a SQL question, there are WordPress components and Core has no efficient mechanism to pull this data that I am aware of. This has long been a problem in Core in my opinion. So: global $wpdb; // group name key $meta_key = ‘_create_new_group’; if (!empty($_REQUEST[‘q’])) { // user input $search = … Read more
You can do it easily with WP_Query: $args = array( ‘date_query’ => array( ‘relation’ => ‘OR’, array( ‘column’ => ‘post_date’, ‘after’ => ‘-2 days’ ), array( ‘column’ => ‘post_modified’, ‘after’ => ‘-2 days’ ) ) ); $query = new WP_Query( $args ); More information about date_query parameter of WP_Query. If, for some reason, you still … Read more
You need to add another join: INNER JOIN $wpdb->postmeta rate_review ON p.ID = rate_review.post_id Add the condition to your where clause: AND rate_review.meta_key = ‘rate_review’ Now you can add it to your SELECT: rate_review.meta_value AS rate_review
I had to use two separate queries. The $wpdb->update syntax cant deal with calculating based on the existing value. But for the other two fields it works. So like this: $table = $wpdb->prefix . ‘woocommerce_downloadable_product_permissions’; $expiry_date = date(“Y-m-d”, strtotime(“+ 30 days”)); $expiry_time = $expiry_date . ‘ 00:00:00’; $wpdb->query(“UPDATE $table SET download_count = (download_count + 1) … Read more
The main problem is how you’re specifying the custom table name (e.g., $wpdb->cf7dbplugin_submits). $wpdb only knows about the “built-in” tables when accessing a table name via $wpdb->xxx. To specify access a custom table name, use {$wpdb->prefix}custom_table_name. The other thing I notice is that, for security purposes, you should never use interpolated variables in an SQL … Read more