SQL Prompt 4 - *STILL* doesn't "get it" when it comes to XML

Provides intelligent code completion for SQL Server editors.

Moderators: David Atkinson, Anu Deshpande, Luke Jefferson

SQL Prompt 4 - *STILL* doesn't "get it" when it comes to XML

Postby mscheuner » Tue Aug 18, 2009 12:44 pm

I'm a bit annoyed - SQL Prompt 4 STILL doesn't "get it" when it comes to SQL XML DML support......

Imagine a table something like this:

Code: Select all
CREATE TABLE MyDemoTable
   (ID INT IDENTITY(1,1) PRIMARY KEY,
    Title VARCHAR(50),
    Payload XML)


If I want to change some content in the "Payload" XML column, I can do this with an UPDATE statement:

Code: Select all
UPDATE MyDemoTable
SET Payload.modify('replace value of ..... with "...." ')


The problem is: those keywords ".value", ".modify" that I type AFTER the XML column name (Payload) ARE CASE SENSITIVE - but SQL Prompt insists on UPPERCASING those.

Yes, I know, I can turn off uppercasing all together - but that's at best a hackish workaround......

Is it really not possible for SQL Prompt to detect, that when I type:

Code: Select all
UPDATE MyDemoTable
SET Payload.


that "Payload" is an XML column, and therefore, if I now proceed to type "modify" and a space or opening parenthesis, that it should never force this "modify" to UPPERCASE ?

What happens now is:

Code: Select all
UPDATE MyDemoTable
SET Payload.modify


and as soon as I type "(" now, I get:

Code: Select all
UPDATE MyDemoTable
SET Payload.MODIFY(


and that's just not valid SQL XML DML syntax anymore.

See this link here for the SQL XML DML keywords:

http://msdn.microsoft.com/en-us/library/ms190798.aspx

All five of those (.query(), .nodes(), .value(), .modify(), .exist() ) are case-sensitive and should definitely be left alone when used on a XML column!


Marc
mscheuner
 
Posts: 39
Joined: Wed Dec 07, 2005 7:17 am
Location: Switzerland

Postby Anu Deshpande » Wed Sep 02, 2009 1:25 pm

Apologies for the delay in replying your post and thank you for your request.

We have logged this in our enhancement request database as SP-2794.
If we get sufficient interest in this feature we’ll considering putting it in a future release.

Kindly let us know if you have any other issues/questions regarding SQL prompt, I'll like to help.
Anuradha Deshpande
Product Support
Redgate Software Ltd.
E-mail: support@red-gate.com
Anu Deshpande
 
Posts: 692
Joined: Mon Apr 20, 2009 3:53 pm
Location: Cambridge


Return to SQL Prompt Previous Versions

Who is online

Users browsing this forum: No registered users and 1 guest

cron