SQL Prompt bug: missing schema in cross-database sequence autocomplete
Alberto
Posts: 10 Bronze 3
in SQL Prompt
Hi,
it seems I can confirm a bug in the autocomplete function.
Let Database1 and Database2 be two different databases on the same server. I have a schema named Schema1 defined in Database1, and a sequence Sequence1 defined within that schema.
When connected to Database1, while writing a SELECT NEXT VALUE FOR Seq... shows Sequence1 in the autocomplete suggestions, and pressing TAB turns "Seq" into "Schema1.Sequence1".
While writing the same statement when connected to Database2, the autocomplete suggestions still shows Sequence1, but pressing TAB leads to "Database1.Sequence1".
I use SQL Server Management Studio 17.9 with SQLPrompt 9.3.1.6690.
it seems I can confirm a bug in the autocomplete function.
Let Database1 and Database2 be two different databases on the same server. I have a schema named Schema1 defined in Database1, and a sequence Sequence1 defined within that schema.
When connected to Database1, while writing a SELECT NEXT VALUE FOR Seq... shows Sequence1 in the autocomplete suggestions, and pressing TAB turns "Seq" into "Schema1.Sequence1".
While writing the same statement when connected to Database2, the autocomplete suggestions still shows Sequence1, but pressing TAB leads to "Database1.Sequence1".
I use SQL Server Management Studio 17.9 with SQLPrompt 9.3.1.6690.
Tagged: