Posted: Thu Mar 25, 2004 4:21 am Post subject: Strange problems in select statement
Acolyte
Joined: 02 Jan 2004 Posts: 53
Hi,
I have never seen such a problem in my life.
Problem 1:
If i parse XML message in MRM Domain i cannot access attributes of XML elements in compute node .I have to use '@', before attribute.This works fine.
eg:For XML data
<level1>
<level2 id='123'></level>
</level1>
if i refer to 'id' as "level1"."level2"."@id" in ESQL....it works perfectly.....But this is not the case with all attributes. . I have to check in debugger or in trace node to really check if th attribute is preceded b "@".Only then i can use "@"...else without '@' itr works fine.....
Problem2:
declare T as Environment.Variables.FlowSpecific."class"[];
SET temp = THE(SELECT ITEM R."avText"."value" FROM T."at"[] as R WHERE R."@id" = '437');
This statement works fine as long as "437" anywhere in first <class>.
Problem 1:
If i parse XML message in MRM Domain i cannot access attributes of XML elements in compute node .I have to use '@', before attribute.This works fine.
eg:For XML data
<level1>
<level2 id='123'></level>
</level1>
if i refer to 'id' as "level1"."level2"."@id" in ESQL....it works perfectly.....But this is not the case with all attributes. . I have to check in debugger or in trace node to really check if th attribute is preceded b "@".Only then i can use "@"...else without '@' itr works fine.....
If the MRM finds a self defined attribute (ie one which it cannot match to your message set) it will be appended with an @ when written to the tree.
So the reason you are sometimes seeing the @ and sometimes not is because sometimes the attributes matches your model and sometimes it is self-defined. So if this attribute is defined i nthe message set then your message is not matching the message set.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum