RC 3.5: viewing definition of tabular functions
Ulrich
Posts: 10
I just noticed a problem that is new in RC 3.5:
when I code
select * from MyTabularFunction(@param1, @param2)
With SQL Promt 3.1 I was able to view the function defintion anytime using Ctrl-space with the cursor at the end of the function name. This is no longer possible as the popup now appears with eht message "no suggestions"
It starts working again if I delete the remaining code of the line, that is
(@param1, @param2)
so it seems RC 3.5 is fooled by the code following the function name.
I would be glad to see the behavior of 3.1 again in the final 3.5!
Thanks
Ulrich
when I code
select * from MyTabularFunction(@param1, @param2)
With SQL Promt 3.1 I was able to view the function defintion anytime using Ctrl-space with the cursor at the end of the function name. This is no longer possible as the popup now appears with eht message "no suggestions"
It starts working again if I delete the remaining code of the line, that is
(@param1, @param2)
so it seems RC 3.5 is fooled by the code following the function name.
I would be glad to see the behavior of 3.1 again in the final 3.5!
Thanks
Ulrich
Comments
Try this:
(1) Open the EngineOptions.xml file (usually in "C:\Documents and Settings\{username}\Local Settings\Application Data\Red Gate\SQL Prompt 3") in your favourite text editor (NOT TextPad though as this seems to corrupt the file for reading by SQL Prompt).
(2) Find the <EnableFastSingleMatchInsertion> element and set its value to "False".
(3) Save the file and see what happens now.
Unfortunately because we added this option quite late in the development cycle it's not exposed through the UI. This is a bit of a long shot so if you're still seeing this problem please let me know. It might be something we'll need to address in the patch release.
Thanks,
Bart
Principal Consultant
bartread.com Ltd
Thank you for your quick reply.
My EngineOptions.xml did not contain the tag you mentioned, so I added it as a new line
<EnableFastSingleMatchInsertion>False</EnableFastSingleMatchInsertion>
(just after the first line <EngineOptions>)
Unfortunately this did not change the behaviour described in my original post.
Looking forward to see a patch :-)
Ulrich
Cheers,
Bart
Principal Consultant
bartread.com Ltd