Should I use wpdb prepare?
I’m new to SQL and am wondering if I need to use wpdb->prepare for the following query to a table I’ve created
I’m new to SQL and am wondering if I need to use wpdb->prepare for the following query to a table I’ve created
I have a WordPress database which was installed in a development environment… thus, all references to the site itself have a fixed IP address (say 192.168.16.2). Now, I have to migrate that database to a new WordPress installation on a hosting. The problem is that the SQL dump contains a lot of references to the IP address, and I have to replace it with: my_domain.com.
anyone encountered this bug that it will work when you are logged in but once you log out it won’t work anymore.
Normally, a MySQL database can be exported and imported using these simple SSH commands:
For whatever reason, I have a post and a page with the same slug name and it causes the db to hang. I can’t alter the slug on either so I need to go manually delete the posts from the database and start over.
Is there anyway I could convert all the posts e have right now on our WordPress install into products using some MySQL query or something like that?
I’m new to WordPress and was wondering why in WordPress API do they tell you to use functions such as prepare(), insert(), get_col(), get_row(), query(), etc. when technically I can use the built-in PHP-SQL functions such as mysqli_query(), mysqli_fetch_assoc(), etc.
I just created a new WordPress site in my server. Normally, WordPress uses MyISAM as the database type. But this time, it created all InnoDB tables! Is this normal? Has WordPress switched to InnoDB in the latest versions?
Here’s my challenge: I have a .csv file which contains 20,000 rows of data.
If there is a WordPress plugin which updates rows in a custom table, but that update encounters a row lock, what happens? E.g. two users simultaneously fire an update on TABLE1, one setting AGE=1 and the other setting AGE=2: