This is yet another post that’s going to be an illustration of how to use $wpdb to quickly update information based on metadata.
And the code provided in that post works but if you’re looking to make it more object-oriented, then there’s more work that can be done.
Before jumping into the actual post, though, it’s important to note that when it comes to object-oriented programming, there’s a lot of work that can go into the class design and creating levels of abstraction.
At some point, you have to draw the proverbial line between when you’re going to use interfaces, how granular your classes are going to be in terms of what they are abstracting, and the like.
And the purpose of this post is to help provide a better object-oriented design but it’s not an exercise is making this as optimal as possible. I do discuss topics like this in another series of posts.
But keep that in mind when reading through the code throughout the rest of the post.
When we’re working on a variety of devices – be it our computers, our tablets, or even our phones – it’s definitely convenient to have access to certain types wherever we are, right?
And with files aside, our phones have such powerful cameras now; it’s nice also to have the ability to store our photos but also to free up space on our phones (although this may be a tertiary issue for you regarding file syncing).
Anyway, there are a lot of services that are available that allow you to store your files in the cloud and to access them anywhere. It’s easy to tout security and privacy and, yes, we can do things on our end like enable two-factor authentication.
But what about the actual files themselves? That is, we can make it more difficult to log in and access the files but what about those on the other side who work at the company responsible for storing the files?
This is not the first time I’ve mentioned this, but one of the challenges that come with talking about writing direct database queries to update information in the WordPress database is that you leave yourself open to something like:
Yeah, but there’s an API to do something just like that.
And, in many cases, that’s right. I’m a big fan of using ’em, too. But there are times where direct, parameterized database queries can be a more optimal choice.
This is, of course, contingent on the environment in which you’re working the requirements of your project.
So this is yet another post that’s going to be an illustration of how to use $wpdb to quickly update information based on metadata (without using something like WP_Query or WP_Meta_Query to handle it).