Feature: Parser Bracket Errors - Microsoft SQL Server Analysis Services and MDX forums-SSAS

Welcome, Guest
Please Login or Register. Lost Password?

Microsoft SQL Server Analysis Services and MDX forums

SSAS Forums

MDX Studio

Feature: Parser Bracket Errors

(1 viewing) (1) Guest

Please post here just questions about MDX Studio. All other questions will be moved to "Analysis Services Forum".

Page: 1

TOPIC: Feature: Parser Bracket Errors

Forum Tools

#1505

Feature: Parser Bracket Errors 10 Months, 1 Week ago Karma: 0

hello Mosha,

thanks for implenting the timer, very useful. :D

I noticed that the parser respond diffrent on (round and squared) bracket errors.

I go a little bit into greater detail, break the problem into small parts and make a solution suggestion.
If i'm typing a mdx statement, sometimes the mdx studio shows me which bracket i close. So i think it knows when a part statement is closed.

It would be helpful if the parser tells me where i made a bracket error. Like in my first example, there is one bracket too much open in the with part. But mxd studio and MSSMS don't react. They both execute the statement and show an error in the column.

first example

Code:



WITH 

  MEMBER &#91;Measures&#93;.&#91;Measure1&#93; AS &#91;&#91;DIM&#93;.&#91;Hierarchy&#93;.CurrentMember.Name 

SELECT 

  { &#91;Measures&#93;.&#91;Amount&#93;, &#91;Measures&#93;.&#91;Measure1&#93; } ON 0

 ,&#91;DIM&#93;.&#91;Hierarchy&#93;.ALLMEMBERS ON 1

FROM &#91;Cube&#93;

In the second example there is a wasted closed bracket in the with part. Mdx studio and MSSMS show me there is a problem in the select part.

second example

Code:



WITH 

  MEMBER &#91;Measures&#93;.&#91;Measure1&#93; AS &#91;DIM&#93;.&#91;Hierarchy&#93;&#93;.CurrentMember.Name 

SELECT 

  { &#91;Measures&#93;.&#91;Amount&#93;, &#91;Measures&#93;.&#91;Measure1&#93; } ON 0

 ,&#91;DIM&#93;.&#91;Hierarchy&#93;.ALLMEMBERS ON 1

FROM &#91;Cube&#93;

In the third example there is a wasted open bracket in the select part. Mdx studio shows me exactly the right position of the error. But it don't see the reason for the error!

third example

Code:



WITH 

  MEMBER &#91;Measures&#93;.&#91;Measure1&#93; AS &#91;DIM&#93;.&#91;Hierarchy&#93;.CurrentMember.Name 

SELECT 

  { &#91;&#91;Measures&#93;.&#91;Amount&#93;, &#91;Measures&#93;.&#91;Measure1&#93; } ON 0

 ,&#91;DIM&#93;.&#91;Hierarchy&#93;.ALLMEMBERS ON 1

FROM &#91;Cube&#93;

In the fourth and last example there is a wasted closed bracket in the select part. Mdx studio and MSSMS shows me there is an error at the "on".

fourth example

Code:



WITH 

  MEMBER &#91;Measures&#93;.&#91;Measure1&#93; AS &#91;DIM&#93;.&#91;Hierarchy&#93;.CurrentMember.Name 

SELECT 

  { &#91;Measures&#93;.&#91;Amount&#93;, &#91;Measures&#93;.&#91;Measure1&#93;&#93; } ON 0

 ,&#91;DIM&#93;.&#91;Hierarchy&#93;.ALLMEMBERS ON 1

FROM &#91;Cube&#93;

Which the round bracket there are similar problems.

I understand that the parser can't be that intelligent like it knows where to close a bracket. But there could be small rules. I think you have them allready implemented and maybe you could expand them a little bit.

My suggestion would be a parser routine which
- first analyze if there is a bracket too much closed and shows the user the position - just a "small" counting routine
- second analyze if there is a bracket too much opend - you could count it on function words like you do it in the select part, but at the moment it doesn't work for the with part. There are the same possibilities. The round or squared brackets have to be closed until the next function word. You couldn't show the user the exact position. But for example if the with part is clean i have to look just on one part of the statement or the oposite. ;)

I think this two simple rules could reduce the searching anger with brackets inside big mdx statements.

Hope wasn't going to much in detail. :lol:
Is the code of the mdx studio open, so that i could maybe sometimes come up with a solution suggestion?

Greetings
MJ

PS: Mosha - your posting timestamp shows that you answering from the past (2007). Are you always ahead of the times (view from the past or behind view from today)? :D

Methos

Fresh Boarder

Posts: 6

The administrator has disabled public write access.

#1533

Re: Feature: Parser Bracket Errors 10 Months ago

Karma: 1

Methos

Thanks for very detailed report. The issue here is that there are some detailed rules about how brackets work with MDX. Since member names can contain any characters, there must be a way for escaping them. So the rules are - open bracket, i.e. [ can be anywhere. Therefore [DIM] is perfectly valid. But closing bracket needs to be doubled, therefore [DIM]] is not valid, but [DIM]]] is valid again.
This is somewhat obscure, but this is the only way to properly support brackets in member names. This rule existed in MDX since 1997, and it is a bit late to change it...

mosha

Admin