if $wpdb->get_results is not sanitized by core code, why we can’t execute different SQL query in it? Because the wpdb class uses (see wpdb::_do_query() ) mysqli_query() (by default) or mysql_query(), and unfortunately these functions do not support multiple queries such as SELECT <query>; INSERT <query>; SELECT <query>. Therefore, if you want to execute multiple SQL … Read more
WordPress fires the updated_{$meta_type}_meta hook which fires after the metadata is updated. In your case, the hook would be updated_post_meta and you could have your function run on that hook instead of the save_post hook.
The $wpdb object is based on ezSQL, it does not add much overhead, so I would not worry about that. Opening a second connection to the database yourself will probably lead to more overhead than using the $wpdb functions. The three queries you have described are ideal queries to do in the database (a small … Read more
You can assign taxonomies to objects saved in tables other than the posts table. WordPress explicitly supports that (e.g. there is the function _update_generic_term_count to update the term count for those types of taxonomies) and even use it for links. I have used it once. Just register your taxonomies as you would for regular post … Read more
If you’ve got 60,000 records, try cleaning post/page revisions; these really accumulate and cause excessively long queries. I’ve seen database sizes drop 90% with huge increases in performance. Run the query below in phpmyadmin or from the command line and then optimize: DELETE a,b,c FROM wp_posts a LEFT JOIN wp_term_relationships b ON (a.ID = b.object_id) … Read more
As you haven’t offered the details on what you’re after, I’ll try to grab them all very briefly. Use the API – public WP_User_Query API functions Basically get_user_by() should be enough for you. Let’s say you fire of your form and the input field name was user_id. So you’d just retrieve the value from the … Read more
My simple and quick solution is the use of a normal $wpdb->query() function: $wpdb->query( $wpdb->prepare(“UPDATE $schedule_table SET rpt = %s WHERE post_id = %d AND start IS NULL AND end IS NULL”, $event_tag, $post_ID ) );
What you did wrong here was to prepare those items in the first place. You only run “data” variables through prepare(). You don’t run table names, or sort directions, or limits through it. These are part of the SQL command itself, they are not data that refers to information which is stored in a column … Read more
You should’nt really be using wp query here, use get_user_meta(); Example: $first_name = get_user_meta(2, ‘first_name’, true);
TL;DR This is not possible with wpdb. Use dbDelta(). Even better, use something else to run raw queries. Explanation wpdb->query() uses the mysql_query() function. From PHP manual: mysql_query() sends a unique query (multiple queries are not supported) to the currently active database on the server that’s associated with the specified link_identifier. In order for that … Read more