Hi Nathan,

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

As the custom posts/fields/taxonomies, are a part of the WordPress database;

pulling this data can only be done through MySQL query-based tables.

Please note: Using this plugin feature requires at least a basic knowledge of SQL. It is assumed that you can create the table in some MySQL data manager (e.g., PHPMyAdmin, MySQL Workbench), and prepare a SQL query that will return the data you need. 

A good way to achieve this can be experimenting using our WPDB SQL Query Constructor tool.

You can also try this other SQL Query helper Tool,

Create a MySQL-query-based table by querying a database,

that one has a wider range of all tables you can choose from your Database outside of WPDB.

- Please note: this tool is not an ultimate query generator. It simply constructs a suggestion of a query. We are constantly working to improve it, but SQL is such a complicated and flexible language that full automation for constructing queries is next to impossible. 

Consequently, the more complicated the query, the higher is the probability that it will not return exactly what you need. So, you will often need to play around with the resulting query.

Please be advised that writing custom SQL Queries or debugging Queries does not fall under what our support covers.

You can check out this official page of WP codex,  for help with writing custom Queries.

Hi Nathan,

Yes. Generally speaking, you should be able to achieve the result with either of these methods, whether it is the first choice that has the "WPDB" structure or the second choice is a more 'generic' MySQL query generator .

As mentioned in the introduction part for both Documentation Pages:

1.  The “WPDB” Constructor helper tool is perhaps more suitable for what you're trying to achieve.

I will just quote the part from the Documentation about this :

The structure familiar to users, is based on different post types, post custom (meta) fields, and taxonomies; all stored in a collection of MySQL tables. 

Querying these elements, however might be somewhat of a headache to someone not that familiar with relative database structures and building SQL queries.

wpDataTables has a built-in WPDB query constructor to help those users. It has a graphical user interface which allows a user to pick the post types, custom/meta fields, and taxonomies, and generates a query and a preview. 

You can modify the query as needed, and create a wpDataTable based on the modified query.

And, we have to take the important note again :

this tool is not an ultimate query generator. It simply constructs a suggestion of a query.

 We are constantly working to improve it, but SQL is such a complicated and flexible language that full automation for constructing queries is next to impossible. 

Consequently, the more complicated the query, the higher is the probability that it will not return exactly what you need. 

So, you will often need to play around with the resulting query.

2. On the other hand, the other generic MySQL query generator Constructor Tool, which you tried already, is perhaps better suited when we are trying to pull data from 'classic structured' SQL Tables, which are more custom Tables, rather than having the "WordPress DB" structure type.

But it can achieve the result, it just has a different way how it shows you the SQL tables when you pick them through the interface.

So, to summarize, I would say the first choice will be better if you are just looking to pull data from the WPDB structure, such as post types, custom/meta fields, and taxonomies.

But then, it gets more complex the more details you add to the Query such as adding specific conditions, etc.

You can check online on various places such as Stack Overflow;

and this official page of WP codex,  for help with writing custom Queries, where you might find posts of other users who achieved a similar use-case.

Our Support is not covering writing or debugging Custom Queries, but I hope this might help to get you started in the right direction.

Thank you.

Hi Nathan,

Unfortunately, we don't currently have anyone we could recommend for something like that.

If any of our developers become available anytime soon, or if we find anyone else to recommend, I will make sure to report back and send the contact to you.