The query itself may need to be optimized (SQL is not my speciality, though). However, don’t forget you can store the results of an expensive operation in cached memory. WordPress offers a Transients API to make things easy. Here’s a quick example: // Try to load the value from cache $transient_key = ‘my_query’; $value = … Read more
Those are not Core entries so far as I know. That means that a plugin or a theme has inserted them. Since I don’t know which plugin or theme it is, or whether you are still using that plugin/theme, I can’t say whether you should delete the entries. If you are still using the plugin … Read more
Have you tried placing the query result to a variable? $resultArray = $wpdb->get_results(“SELECT * FROM properties”)
$current_time = current_time(‘mysql’); $querystr = ” SELECT * FROM {$wpdb->prefix}usermeta WHERE meta_key=’bday_unix’ AND DATE_ADD( from_unixtime(meta_value), INTERVAL YEAR( ‘{$current_time}’ ) – YEAR( from_unixtime( meta_value ) ) YEAR ) BETWEEN ‘{$current_time}’ AND DATE_ADD( ‘{$current_time}’, INTERVAL 30 DAY )”; Should work, I think.
Since your questions are quite vast and not completely WordPress related, I will stick to your main question. The answer is: Yes. As long as you have it in different directories and don’t use the same prefix for their database tables or have a separate database for each (which means you can stuff more than … Read more
Unfortunately, it seems that you have now learned the hard way that you should not: trust only your web hosting company to keep your data intact, or keep your backups on your web server. Sadly, restoring your WordPress installation — if at all possible — will most likely not be easy! You might be able … Read more
The granularity of data in your example suggests that custom field (more so one with multiple values) would be wrong choice in first place. Think about it like this: only one dog might weight precisely 35.5kg — that is type of data appropriate for custom field multiple dogs (or dog breeds) might be of medium … Read more
In order to make the wp_posts(ID) a REFERENCE for the FOREIGN KEY, you should also set the wp_pageviews.ID‘s attributes as UNSIGNED and keep the same data type for the wp_pageviews.ID as (bigint) . Let me know if this helps you.
This seems to be a problem with “orphaned SELECT statements”. It is described here in more detail. One solution would be to create a temporary table and modify my_acquireuserpasswd to save data to temp_table BEGIN DECLARE passwdtemp VARCHAR(64); DECLARE temp VARCHAR(4000); START TRANSACTION; SELECT id, passwd INTO uid1, passwdtemp FROM users WHERE name = name1; … Read more
MySQL errors after a WordPress clone