How can we help you today? How can we help you today?
tentrade
Hello Alex. I am so sorry for not responding to you. I had not checked back here since you posted your replies and the emails had escaped my attention. I just now came here to look at it because I got the message about the update being available and I saw that this issue had been addressed. Yes, that looks like it did it! Thank you. This is actually a more important subject than some people might think. I recently was "tripped" up by not prefacing a string with the "N". I had never thought it actually had any practical impact and that all conversions were taken care of implicitly where needed. However, I had a query that wasn't working correctly and it baffled me, until I added the "N" and magically it worked! From that moment on I realized that it IS necessary to put the "N" before unicode strings. I cannot remember the exact query that this problem occurred in but if I do I will post it. This leads me to another extension request for this feature. Do you think we could make it add the "N" in places other than assignments? For example in comparisons? What I mean is, take the following simple select statement: SELECT * FROM   table1 WHERE  column1 = 'mystring'; If column1 is a Unicode string, then could it also add an "N" before 'mystring'? P.S. SSMS 18 Preview is available now. Is there a timeline on when SQL Prompt will be available for it? I notice that on my system that SQL Search IS working in SSMS 18 but sadly SQL Prompt is not. / comments
Hello Alex.I am so sorry for not responding to you. I had not checked back here since you posted your replies and the emails had escaped my attention. I just now came here to look at it because I g...
0 votes