Going more through a query builder functionality in Studio Pro, I noticed a strange behavior which might or might not be a bug. That depends on whether I am using that feature correctly. Let me describe a perceived issue in my mind (see attached screenshot): To make it simpler, I will use the example of four tables used in my screenshot: company_name, account_bills, accounts and company_mm_accounts, company_mm_accounts is man-to-many while all the others are one-to-many relations. Issues (or at least what I consider an issue form a user perspective):

1. Once tables are dropped to the query pane, the automatically build query cannot be altered in that module by changing the order in which joins are made. By that I mean I cannot change what is my starting table "from" followed by next join and so on. That is predetermined for me by the builder.

2. When I change the joins type from inner to left or right, etc., I cannot use table alias names. If I do, the changes I made to the joins via GUI are reset and all joins are set back to a straight join or old type of join (select * from t1, t2, t3, t4 where ...) That's not what I want.

3. There is something amiss with the way the query builder assigned schema names. It assigns schema name to the columns but oddly enough it does not do so for tables which is actually what I would expect it to do so the query does not produce an error at the run time (table cannot be found).

4. It would be nice if you allowed to correct the query in the Query text section itself of your query builder so it could be saved rather than taking it out to be fixed in SQL editor.

5. Finally, I could not find/determine a way on how one could use the query tool for nested select statements. Is it even possible?

As I mentioned, these are observations based on my current, perhaps limited knowledge of your product (I hope) and this is something I missed. Again, thanks in advance for your time and reply.