webMethods

webMethods

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  Search in Tamino

    Posted Wed September 25, 2002 10:51 AM

    I have “Element simple” with type “xs:string” in my base. His name is “EntryID”. his value is “00”.
    I can not find it with request: …[EntryID=“00”].
    But if value is on range “01” - “99” - all right.
    And if value is “0” and
    request is …[EntryID=“0”] - all right two.
    Is it right?
    :confused:


    #Tamino
    #webMethods
    #API-Management


  • 2.  RE: Search in Tamino

    Posted Wed September 25, 2002 05:44 PM

    Hello CBH,

    is your problem occurring with the XML:DB API, or is it a more general problem?

    Please post the Tamino Schema that you are using for your documents, then we will investigate the problem further.

    Thanks,
    Trevor.


    #API-Management
    #Tamino
    #webMethods


  • 3.  RE: Search in Tamino

    Posted Fri September 27, 2002 10:33 AM

    Hello,Trevor.
    My mind - this problem is more general. May be it linked with data-compression. Althoug, compression for index…
    My schema:

    <?xml version = "1.0" encoding = "UTF-8"?>
    <xs:schema xmlns:xs = “XML Schema” xmlns:tsd = “http://namespaces.softwareag.com/tamino/TaminoSchemaDefinition”>
    xs:annotation
    xs:appinfo
    <tsd:schemaInfo name = “DCMSchema”>
    <tsd:collection name = “DCM”></tsd:collection>
    <tsd:doctype name = “DCMXML”>
    tsd:logical
    tsd:contentopen</tsd:content>
    </tsd:logical>
    tsd:physical</tsd:physical>
    </tsd:doctype>
    <tsd:doctype name = “DCMnonXML”>
    tsd:nonXML</tsd:nonXML>
    </tsd:doctype>
    tsd:adminInfo
    tsd:versionTSD3</tsd:version>
    tsd:created2002-06-25T14:16:55.177+03:00</tsd:created>
    tsd:modified2002-06-25T14:24:25.114+03:00</tsd:modified>
    </tsd:adminInfo>
    </tsd:schemaInfo>
    </xs:appinfo>
    </xs:annotation>
    <xs:element name = “DCMXML”>
    xs:complexType
    <xs:choice minOccurs = “0” maxOccurs = “unbounded”>
    <xs:element name = “EntryID” type = “xs:string”></xs:element>
    <xs:element name = “LoginName” type = “xs:string”></xs:element>
    <xs:element name = “PassWord” type = “xs:string”></xs:element>
    <xs:element name = “Date_Time” type = “xs:string”>
    xs:annotation
    xs:appinfo
    tsd:elementInfo
    tsd:physical
    tsd:native
    tsd:index
    tsd:standard</tsd:standard>
    tsd:text</tsd:text>
    </tsd:index>
    </tsd:native>
    </tsd:physical>
    </tsd:elementInfo>
    </xs:appinfo>
    </xs:annotation>
    </xs:element>
    <xs:element name = “From” type = “xs:string”>
    xs:annotation
    xs:appinfo
    tsd:elementInfo
    tsd:physical
    tsd:native
    tsd:index
    tsd:standard</tsd:standard>
    tsd:text</tsd:text>
    </tsd:index>
    </tsd:native>
    </tsd:physical>
    </tsd:elementInfo>
    </xs:appinfo>
    </xs:annotation>
    </xs:element>
    <xs:element name = “Theme” type = “xs:string”>
    xs:annotation
    xs:appinfo
    tsd:elementInfo
    tsd:physical
    tsd:native
    tsd:index
    tsd:text</tsd:text>
    </tsd:index>
    </tsd:native>
    </tsd:physical>
    </tsd:elementInfo>
    </xs:appinfo>
    </xs:annotation>
    </xs:element>
    <xs:element name = “Text” type = “xs:string”>
    xs:annotation
    xs:appinfo
    tsd:elementInfo
    tsd:physical
    tsd:native
    tsd:index
    tsd:text</tsd:text>
    </tsd:index>
    </tsd:native>
    </tsd:physical>
    </tsd:elementInfo>
    </xs:appinfo>
    </xs:annotation>
    </xs:element>
    <xs:element name = “AppendURI” type = “xs:anyURI”></xs:element>
    </xs:choice>
    </xs:complexType>
    </xs:element>
    </xs:schema>

    Bye-bye.

    :slight_smile:


    #Tamino
    #webMethods
    #API-Management


  • 4.  RE: Search in Tamino

    Posted Fri September 27, 2002 09:00 PM

    Hello CBH,

    unfortunately, I can’t recreate the problem you are experiencing!

    Using the schema you posted and this instance:
       <?xml version="1.0" encoding="UTF-8"?>
       
          00
          xXx
          xXx
          <Date_Time>Today</Date_Time>
          A
          B
          C
          http://www.softwareag.com/
       

    The query /DCMXML[EntryID=“00”] returns the document correctly:
       <?xml version="1.0" encoding="iso-8859-1"?>
       <ino:response xmlns:ino=“http://namespaces.softwareag.com/tamino/response2” xmlns:xql=“http://metalab.unc.edu/xql/"><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<xql:query>/DCMXML[EntryID="00”]</xql:query>
          <ino:message ino:returnvalue=“0”>
             ino:messagelineXQL Request processing</ino:messageline>
          </ino:message>
          xql:result
             
                00
                xXx
                xXx
                <Date_Time>Today</Date_Time>
                A
                B
                C
                http://www.softwareag.com/
             
          </xql:result>
          <ino:message ino:returnvalue=“0”>
             ino:messagelineXQL Request processed</ino:messageline>
          </ino:message>
       </ino:response>

    I tested this using Tamino 3.1.2.1 and querying from Internet Explorer.

    Could you please send details of your documents and how you are submitting the query (Browser, API, etc.)?

    An interesting test for you to try would be to execute the query using ino:explain().
    For example: _xql=ino:explain(/DCMXML[EntryID=“00”])

    This gives me the response:
       <?xml version="1.0" encoding="iso-8859-1"?>
       <ino:response xmlns:ino=“http://namespaces.softwareag.com/tamino/response2” xmlns:xql=“http://metalab.unc.edu/xql/"><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<xql:query>ino:explain(/DCMXML[EntryID="00”])</xql:query>
          <ino:message ino:returnvalue=“0”>
             ino:messagelineXQL Request processing</ino:messageline>
          </ino:message>
          xql:result
             <ino:explanation ino:preselection=“FALSE” ino:postprocessing=“TRUE”/>
          </xql:result>
          <ino:message ino:returnvalue=“0”>
             ino:messagelineXQL Request processed</ino:messageline>
          </ino:message>
       </ino:response>

    Which is correct for the schema given - preselection is “FALSE” because EntryID doesn’t have an index, thus postprocessing is “TRUE” because the post processor is used to find the result.
    Perhaps the response will show you something interesting on your system.

    I hope that helps,
    Trevor.


    #Tamino
    #API-Management
    #webMethods


  • 5.  RE: Search in Tamino

    Posted Fri October 04, 2002 09:55 AM

    Excuse me. It is my bug.
    :rolleyes:


    #webMethods
    #API-Management
    #Tamino