Hello again A3igner.

Yes, I see. I tried it locally, and it is doing the same thing on our end. This is because the dot ( . ) is a delimiter that usually represents a new column, and it is trying to search for columns within the existing column.

Like mentioned in our documentation:

Please note that MySQL query constructor is not an ‘ultimate generator’, it should be treated as helper for constructing a suggestion of a query, by trying to ‘guess’ what you want. We are constantly working to improve it, but SQL is such a complicated and flexible language that fully automating the process for constructing queries is hardly possible. Consequently, the more complicated your request is, the higher is the probability that it will not return exactly what you need. Play around with the resulting query to achieve better results.

So, with this in mind, you can modify the query it generates, and add the ".VI" to the columns that contain it, and the table will be generated successfully (see attachment).

Or, you can simply generate your own query by creating the table using the first option (Create a table linked to an existing data source):

SELECT LScore2_VI.`tradedate`,
       LScore2_VI.`ANDR.VI`,
       LScore2_VI.`BWO.VI`,
       LScore2_VI.`CWI.VI`,
       LScore2_VI.`CAI.VI`,
       LScore2_VI.`EBS.VI`
FROM LScore2_VI

Best regards.

Well, A3igner, it is working in our plugin as well if you pass the IDs correctly.

The thing is that you're using the SQL Query Constructor, and I must repeat:

MySQL query constructor is not an ‘ultimate generator’, it should be treated as helper for constructing a suggestion of a query, by trying to ‘guess’ what you want. We are constantly working to improve it, but SQL is such a complicated and flexible language that fully automating the process for constructing queries is hardly possible. 

It trying to guess what you want is what's causing the error - it's guessing that a second delimiter is actually a column within a column - that's why it's reporting that it has no values - it's looking for something that's not actually there.

I agree that it shouldn't manipulate the column heading, and I will forward this to our development team, so they can work on a fix for some of the future releases.

Best regards.