query (Apply a query to a table)

The query transaction applies a query to a table.


A query is essentially a transformation on the table that selects a subset of its rows, reorders rows based on one or more sort criteria, summarizes the data, and so on. The result is conceptually another table. Once a query is set using the query transaction, the values in the result table may be retrieved with the getdata transaction.

Query string

The query string in the HTTP header must contain the following parameters:

Specify the name of the API transaction.
Specify the version of the API that should handle the requested transaction.

For the most up-to-date version, use apiversion=3.

Specify a valid 1010data user name.
Specify a valid password for the 1010data user name provided to the uid parameter.
Note: The pswd value should be the encrypted password returned from the login transaction.
The session ID for the current API session.

This value is returned by the login transaction and must be provided to every transaction (except login).

kill (optional)
Valid values for kill are as follows:
Terminate the existing session and start a new one.
Do not terminate the existing session.

If no session exists, a new one will be created. If a session does exist, an error is returned.

Note: If kill=no and a session is active, the system returns an error.
Log in and possess the existing session.
Authenticate with the system but do not kill, possess, or start any session.

The default is yes.

XML input to server

Input is provided to the API transaction via an XML specification. The outer-most element of the input specification is the <in> element. All input elements and data must be contained by <in>.

The full name of a table. Table names are specified as a full path to the location of the table, e.g., directory1.directory2.directory[N].table.
A list of operations for the system to conduct on a table. This is effectively a 1010data macro.
Note: The <ops> element is required. If you want to return a complete table, you must provide an empty <ops> element that does not contain a 1010data macro.

If <ops> contains one or more <colord> operations, the query transaction takes them into account (i.e., the columns reported in the result will be only those columns selected in the <colord> operations, and they will appear in the order specified in the <colord> operations).

XML response from server

A response from the server contains the following elements:

The return code generated by the transaction. For a list of return codes, see Return codes.
The message returned by the system. Specific messages correspond to specific return codes.
The number of rows in the table returned.
A 1010data XML table tree. To see the full XML specification for the table tree, see Table Tree.

The <table> element (see Table Tree) essentially describes the columns of the result. It is equivalent to the result table with zero rows of data (i.e. the <data> element is empty.) The table tree does not contain <title>, <sdesc>, <ldesc>, <link> or <maxdown>. In the event of an error, only the return code and error message are returned.

Query string example


XML input example

        <link table2="pub.doc.retail.product" col="sku" col2="sku" suffix="_sm"/>
        <sel value="transid=1400190251"/>

XML response example

    <msg>query successful</msg>
            <th name="trans_date" type="i" fixed="0">Date</th>
            <th name="store" type="i" fixed="0">Store</th>
            <th name="xsales" type="f" fixed="0">Extended