SQL Prompt 5 **STILL** not getting *it* with XML functions..

[mscheuner]

Folks, this is disappointing - since about V2 or V3, I've been trying to explain that SQL Prompt *CANNOT* capitalize the XML XQuery function names as provided by SQL Server - and it still does....

Imagine a table with an XML column called "EntryData" - when I start typing:

SELECT EntryData.value(caret is here)
FROM dbo.MyTable

then I'm *CLEARLY* trying to use one of the five XML data type methods (.exist(), .modify(), .nodes(), .query(), .value()) - see here: http://msdn.microsoft.com/en-us/library/ms190798.aspx

Those XML data type methods are **CASE-SENSITIVE* - so SQL Prompt should *NEVER* uppercase those! Please!!

Unfortunately, if I press the space in my query being written in the above sample, I'm left with:

SELECT EntryData.VALUE
FROM dbo.MyTable

and now my XML function is no longer valid - I have to go back and manually turn it to lowercase again.

Is it really not possible to

- detect that the column I'm operating on is of type "XML"
- the string I just typed is one of the five mentioned above (that is a complete list)
- and in this case - just do *NOT* kick in the UPPERCASING (which I like otherwise - great feature - JUST NOT HERE!)

[TSchwab]

You are absolutely right.

I posted the problem in SQL-Prompt 4.0 and got the following answer:

[TSchwab]

By the way, here is the link to my forum post: http://www.red-gate.com/MessageBoard/viewtopic.php?t=10403

_________________
Regards,

Thorsten

[mscheuner]

I was a bit saddened to hear about the "final preview version" of SQL Prompt 5 being out, and this issue is **STILL** **NOT** **FIXED** .......

[AndyIrving]

agree, this is very frustrating!

[Luke Jefferson]

You're right, it's a frustrating flaw, and I completely agree with your complaint. I've run into this myself a few times when writing queries.

If it were a straightforward fix, believe me, we would have tackled it already, but sadly it's part of the parser and whilst the team were keen to work on improving certain aspects of it, there was no scope to look at modifying that part of the code base in this release; the last rewrite of the parser took twelve months.

We do try our best to accommodate as many user requests as possible, but we can't solve all the problems due to resource limitations. I understand this is really frustrating for you and it's a valid complaint; it isn't that we think it's fine as it is or that it is not worth fixing, it's just that we have had higher priority issues to tackle. All that said, I will do my best to push for this fix in the future and would ask readers of this post to chip in to add weight to the case.

Luke Jefferson
Product Manager
Red Gate Software

[AndyIrving]

Sorry if this sounds a little harsh, but... new in this release is the removal of sql refactor and only some of those features put into sql prompt, plus script as alter?