I was wondering the exact same thing. Ideally I'd like the reference to be fully qualified ([database_name].[schema].[object]) upon code completion. I haven't found a way to do this for SQL Server code.
I hope you understand why it qualifies your object — you have the synonym in PUBLIC schema with the same name.
PUBLIC is seen in every context and IDE actually does not know which particular objects you mean when you type. So it tries to detect it by the item you clicked in the completion list.
Anyway, we understand the issue, and I think it is rather common for Oracle that one can have such kinda synonyms.
So, here is the ticket in our tracker, please share your thoughts there as well.
I'd actually LIKE to have schema completion, but I'm not clear how to turn it on. I'm on PG 9.4 DB with ~50 different schemas. Making the selection below doesn't qualify the object with a schema name. How do I enable that?
Correct, the object names are unambiguous 80% of the time. While the names are unambiguous, both coding convention on the team and the fact that I work out of many schemas at once mean that I always qualify object names with a schema. A typical SQL query crosses 2 schemas (_clean, and _deliver, from Kimball's "subsystems of ETL"). http://www.kimballgroup.com/2007/10/subsystems-of-etl-revisited/
I was wondering the exact same thing. Ideally I'd like the reference to be fully qualified ([database_name].[schema].[object]) upon code completion. I haven't found a way to do this for SQL Server code.
It is not clear — do you want the objects NOT to be auto-qualified?
@Maxim, personally I would like to be able to choose if the Schema name should be prefixed, or removed totally.
So it is possible that you'd prefer object NOT TO BE clarified even if there are collisions in names?
Normally there is no clash, at least not for Oracle Development, a name is unique within a schema.
What I would like, from the above example, when selecting "CLA_EVENT (TIA)" I would like it to type out "CLA_EVENT", not "TIA.CLA_EVENT".
The code becomes unnecessary cluttered with the schema name.
I hope you understand why it qualifies your object — you have the synonym in PUBLIC schema with the same name.
PUBLIC is seen in every context and IDE actually does not know which particular objects you mean when you type. So it tries to detect it by the item you clicked in the completion list.
Anyway, we understand the issue, and I think it is rather common for Oracle that one can have such kinda synonyms.
So, here is the ticket in our tracker, please share your thoughts there as well.
https://youtrack.jetbrains.com/issue/DBE-3194
I'd actually LIKE to have schema completion, but I'm not clear how to turn it on. I'm on PG 9.4 DB with ~50 different schemas. Making the selection below doesn't qualify the object with a schema name. How do I enable that?
I have the same issue as Mark, but in my case I am using SQL Server rather than Postgres. Would love to know how to get this to work.
Mark. But the names are not ambiguous, right?
Correct, the object names are unambiguous 80% of the time. While the names are unambiguous, both coding convention on the team and the fact that I work out of many schemas at once mean that I always qualify object names with a schema. A typical SQL query crosses 2 schemas (_clean, and _deliver, from Kimball's "subsystems of ETL"). http://www.kimballgroup.com/2007/10/subsystems-of-etl-revisited/
Then, please give us the option to turn it on and off ....
Guys, please follow this issue: https://youtrack.jetbrains.com/issue/DBE-3194