MySQL

Export Yoast Keywords from MySQL/phpMyAdmin

This query pulls the post id, title, permalink, and focus keywords. You could modify this to pull the post meta description and title as well if you wanted. Change post_type to page if you want to pull pages. SELECT wpp.post_title, wpp.ID, wpp.post_date, mt1.meta_value as focus_keyword, REPLACE( REPLACE( REPLACE( REPLACE( wpo.option_value, ‘%year%’, DATE_FORMAT(wpp.post_date,’%Y’) ), ‘%monthnum%’, DATE_FORMAT(wpp.post_date, … Read more

string literals in query

I misplaced a single quote. This query worked for me and solved my problem. update wp_postmeta set meta_value= concat( ‘a:1:{s:3:”url”;s:28:”‘, meta_value, ‘”;}’ ) where meta_key = ‘_woofv_video_embed’

Copy usermeta value where ID matches in the same table

use this code, it may help you $users = get_users($args); if($users) { foreach($users as $user) { $user_id = $user->ID; $shipping_first_name = get_user_meta($user_id, ‘shipping_first_name’, true); if($shipping_first_name) { update_user_meta( $user_id, ‘first_name’, $shipping_first_name); } } } for $args – refer link https://codex.wordpress.org/Function_Reference/get_users

Postgres equivalent to MySQL’s \G?

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;

Postgres equivalent to MySQL’s \G?

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;

Postgres equivalent to MySQL’s \G?

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;

How to set MYSQLI_OPT_INT_AND_FLOAT_NATIVE option

That’s why I’m wondering why is WordPress stuck to this pre-PHP-5.3 limitation. Because WordPress has made the decision to support PHP 5.2 due to the large number of hosts that continue to use it. This is an ongoing debate and there’s no point rehashing it all here. But this means that I have to know … Read more

+ More