Query using "mapping-type=object"

, ,
1

Dear friends ,

I built a joined query, but for a filter i could not use the nodeReference shema elements.

How can i success it.
I got the error code

<ino:message ino:returnvalue=“8544”>
<ino:messagetext ino:code=“INOXME8544”>Query using “mapping-type=object” cannot be evaluated.</ino:messagetext>
</ino:message>

brgs
iwama

2

Can we have your schemas, data and the query?

3

My tsd:

<?xml version = "1.0"?>
<xs:schema xmlns:xs = “XML Schema” xmlns:tsd = “http://namespaces.softwareag.com/tamino/TaminoSchemaDefinition”>
xs:annotation
xs:appinfo
<tsd:schemaInfo name = “Test”>
<tsd:collection name = “Test”></tsd:collection>
<tsd:doctype name = “Customer”>
tsd:logical
tsd:contentclosed</tsd:content>
</tsd:logical>
</tsd:doctype>
<tsd:doctype name = “Order”>
tsd:logical
tsd:contentclosed</tsd:content>
</tsd:logical>
tsd:physical</tsd:physical>
</tsd:doctype>
tsd:adminInfo
tsd:versionTSD3</tsd:version>
tsd:created2002-08-17T21:51:47.585+08:00</tsd:created>
tsd:modified2002-08-17T21:51:47.585+08:00</tsd:modified>
</tsd:adminInfo>
</tsd:schemaInfo>
</xs:appinfo>
</xs:annotation>
<xs:element name = “Customer”>
xs:complexType
xs:sequence
<xs:element name = “CustomerNo” type = “xs:string”></xs:element>
<xs:element name = “CustomerName” type = “xs:string”></xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name = “Order”>
xs:complexType
xs:sequence
<xs:element name = “OrderNo” type = “xs:string”></xs:element>
<xs:element name = “CustNo” type = “xs:string”>
xs:annotation
xs:appinfo
tsd:elementInfo
tsd:physical
tsd:native
tsd:objectRef
tsd:collectionRefTest</tsd:collectionRef>
<tsd:accessPredicate operator = “=”>
tsd:nodeRef/Customer/CustomerNo</tsd:nodeRef>
</tsd:accessPredicate>
</tsd:objectRef>
</tsd:native>
</tsd:physical>
</tsd:elementInfo>
</xs:appinfo>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>

and my xml:

<?xml version="1.0"?>

1
David


2
Sunny


5
1


and my X-Query:

/Order[OrderNo=5]/CustNo/

Please help!

4

It seems like that filters are not fully supported for a foreign doctype at this moment.
Tamino is just able to search for primary documents and resolve foreign documents though access predicate.
However I found that some filters are already work. But it involves postprocessing engine.

The situation and some workarounds are described in Tamino documentation at rather great length. Check Advanced Concepts/From Schema to Tamino/Document Composition.

For full joins support let’s wait for XQuery to be implemented.

[This message was edited by Alexander on 18 Aug 2002 at 10:11.]