Feature request
I've been using SQLPro solidly for the past few days against Azure SQL, and I noticed that table names are generally detected well for auto-completion, but not so for bare column name that I know are part of a table (e.g. in a where clause) except when I realised that if I prefixed the column name (in the where clause) by the table name then a dot then start typing the column, then the auto-suggestion would kick in with good suggestions. Similarly if I add a single-letter table alias, and use that first then a dot etc, auto-suggestion would also kick in. This is different to what I was used to in another SQL client, where I didn't need to 'provide a helper' with the table name, i.e. I could type the column name in the where clause, and the auto-suggest would suggest the column, upon entering one or 2 chars, whereas in SQLPro this would not work.
I can imagine auto-suggest is a tricky thing when queries get more complicated, and I don't want to necessary request because I could be ignorant to the challenges of making it work well. I wondered if the approach in SQLPro was a decision based on trying to make it easier for when queries get complicated.
Thanks.
Product
SQLPro Studio
App version
2026.223 (Build 111281)
Platform
macOS
Installation source
Website download
Feature request
I've been using SQLPro solidly for the past few days against Azure SQL, and I noticed that table names are generally detected well for auto-completion, but not so for bare column name that I know are part of a table (e.g. in a where clause) except when I realised that if I prefixed the column name (in the where clause) by the table name then a dot then start typing the column, then the auto-suggestion would kick in with good suggestions. Similarly if I add a single-letter table alias, and use that first then a dot etc, auto-suggestion would also kick in. This is different to what I was used to in another SQL client, where I didn't need to 'provide a helper' with the table name, i.e. I could type the column name in the where clause, and the auto-suggest would suggest the column, upon entering one or 2 chars, whereas in SQLPro this would not work.
I can imagine auto-suggest is a tricky thing when queries get more complicated, and I don't want to necessary request because I could be ignorant to the challenges of making it work well. I wondered if the approach in SQLPro was a decision based on trying to make it easier for when queries get complicated.
Thanks.
Product
SQLPro Studio
App version
2026.223 (Build 111281)
Platform
macOS
Installation source
Website download