You have 2 two problems here: – You can’t use $wpdb-> with custom tables because [postmeta, posts, …] are variables in the class $wpdb. – WHERE ‘id’= 2 is not correct WHERE id = 2 So it should work: global $wpdb; $table_name = “_customtable”; $retrieve_data = $wpdb->get_results( “SELECT * FROM $table_name WHERE id = 2” … Read more
I’m not familiar enough with MySQL to know what the \G option does, but based on the documentation it looks like the psql \x option might do what you want. It’s a toggle, though, so you do it before you submit the query. \x select * from sometable;
I’m not familiar enough with MySQL to know what the \G option does, but based on the documentation it looks like the psql \x option might do what you want. It’s a toggle, though, so you do it before you submit the query. \x select * from sometable;
I’m not familiar enough with MySQL to know what the \G option does, but based on the documentation it looks like the psql \x option might do what you want. It’s a toggle, though, so you do it before you submit the query. \x select * from sometable;
Apparently both wattp_users and wattp2_as_score tables have a column named score_as. Put a prefix with the table name before every mention to score_as column, just as you did with the ID (e.g. wattp2_users.ID) to avoid beeing ambiguous.
Look into MySQL Wildcards. The correct MySQL Query for your search should be WHERE tb_posts.post_content LIKE “%example.com%” You should also be sure that you only target published posts (in contrast to nav_menu_items, revisions etc). Expand your WHERE with this: AND tb_posts.post_type IN (‘post’,’page’,*All Posttypes you use additionally*) AND tb_posts.post_status=”publish” So your complete Query should look … Read more
that was easy to do directly in sql: UPDATE wp_posts SET post_content = replace(post_content,'</div>\r\n\r\n<div id=”postbottom”>’,'</div><div id=”postbottom”>’);
According to the Codex, the delete method will not accept the LIKE operator. You’ll be better off just using the query method. $query = $wpdb->prepare(“DELETE FROM $wpdb->posts WHERE post_type=”flamingo_inbound” AND post_content LIKE %s”, ‘%’.$mail.’%’); $wpdb->query($query); Hopefully $mail doesn’t have a % or _ character otherwise you need to escape it before you build $querylike so: … Read more
To do that, create custom post type to store info. You do not need to create any custom table as your every record will be saved as a unique post in your custom post type. For detailed assistance, please have a look at the documentation here: https://codex.wordpress.org/Function_Reference/register_post_type Let us know if there is any confusion. … Read more
InnoDB is insanely picky about it’s config; if something’s not right, it’ll just give up and go home. To make a change to the log file size without data loss: Revert any config changes you’ve made to the log file size and start MySQL again. In your running MySQL: SET GLOBAL innodb_fast_shutdown=0; Stop MySQL Make … Read more