Script does not open new tab in Macos version of Azure Data studio

[patoJamriska]

Insatlled the extension
tried opening the menu and select the insert option
nothing happens after.

[pacoweb]

Unfortunately I can't reproduce the error because I don't have Macos. I will keep the incident open in case someone can help me. I'm sorry

[sunilred]

Hi. Great extension idea but like Pato mentioned, it does not seem to work on MacOS (latest version). There are no error messages. Just nothing happens.
Happy to help with testing if you needed.

[sunilred]

Hi. Great extension idea but like Pato mentioned, it does not seem to work on MacOS (latest version). There are no error messages. Just nothing happens. Happy to help with testing if you needed.

Hi. I just realised that the "Script table as DELETE" works but none of the other options work. So hopefully it is an easy fix.

[pacoweb]

Thanks @patoJamriska and @sunilred
I´ll try find the issue.
One question: any message in ouput window when operation fails?

[sunilred]

Nothing appears in the output. If the command works, like the DELETE SCRIPT, then it appears in the output pane.

[pacoweb]

Hi,
I have another question @patoJamriska and @sunilred
The clipboard´s options are working?
Thanks

[sunilred]

The clipboard option is not working either except for the DELETE SCRIPT option.

[pacoweb]

When you (@sunilred) can, try this to see if we get more info in the output window

Set the log level to Trace and then see in the ouput window if there is more info

To change the log level, from the Command Palette (Ctrl/Cmd + Shift + P), run the Developer: Set Log Level...
Ref

Thank you so much!

[sunilred]

I changed the log level to trace. The extension is now working fine. I tried SELECT, UPDATE, DELETE and INSERT and they all work fine. Nothing appears in the log trace. I changed the output back to info/default and it is all working fine.

The only difference I did in the last hour or so is that the connection string to the database (Azure SQL) previously did not have any database set, and I changed the default to a particular database. I wonder if that made it work fine.

[pacoweb]

@sunilred Well seen! I'm going to investigate a little more. Thanks a lot!

[pacoweb]

@sunilred I have published a new version of the extension (0.6.2). When you can, you could try to test it leaving the default database name in the connection window empty. Thank you!

[sunilred]

Hi Paco, I tried the new version 0.6.2 and unfortunately, it still didn't work if the connection did not have the default database parameter set. It works fine if I assign a default database.

[pacoweb]

@sunilred Oh, what a shame. I'll try again next week or look for help in the azuredatastudio repository. Thanks for the work!

[pacoweb]

@sunilred y @patoJamriska
I have uploaded a new version (0.6.3). The problem was not MacOs but the connection to Azure SQL Server instances. I have reproduced the problem and have been able to test the fix. If you can try it I would greatly appreciate it. Thanks!
#22