Category: Notes (Page 14 of 50)

When retrieving data, there times where you may want to change the WHERE clause in WordPress. That is, depending on what you’re retrieving, you may want to filter what it’s searching.

A favorite, but It’s not that kind of filter.

And that’s exactly what a WHERE clause does. But just as we’ve looked at content in other posts, we can alter the WHERE clause via the WordPress API.

In previous posts, I’ve covered:

• Displaying the last query, which is useful when doing light debugging.
• Selecting `DISTINCT` records
• Performing a `JOIN` on two tables

Here, I’ll show how to use the API to change the WHERE clause so you’re not having to do so through a custom query.

Continue reading

In a previous posts, I’ve talked about how to:

• View the last query that WordPress executed
• Select `DISTINCT` records in WordPress

There’s a lot more to do than just viewing the last query and selecting distinct rows, though. For example, you can also JOIN two tables in WordPress without having to write raw SQL.

So to be consistent with some of the previous posts, I thought I’d share how to do this using the WordPress API .

Continue reading

If you need to write a query against the WordPress database, grab a reference to $wpdb and get to work, right?

In some instances, sure. I’m not opposed to this. After all, the API exists for a reason. But sometimes, I think we bypass built-in APIs. We go straight for $wpdb without looking to see if other hooks already exist.

If a hook exists, why not use it? It’s one level of abstraction above the database and it uses the native API.

As mentioned in a previous post, I want to cover a few ways to customize queries that run against the database.

Case in point: selecting DISTINCT records from WordPress. Continue reading

Have you ever had the, ahem, pleasure of customizing the WordPress query? One of the most useful things in debugging is displaying the last WordPress query.

Let’s say you’re working with taxonomies and/or post types and you’re passing custom parameters around. And then, you want to setup some debugging to see exactly what’s hitting the database.

This is helpful for a variety of reasons if for no other reason than to see what is running against the database. It gives you insight on what you’re requesting and thus what you’re presenting to the user.

Anyway, writing code to do this is easy.

Continue reading