xquare

Samples summary

XQuare Fusion 1.1


Notice: Read this document if you need to get off-the-shelf examples of XQuare Fusion use in typical situations. It should be used as a practical complement to reference guides and manuals.

This document describes the use-case samples included in the XQuare Fusion distribution.

XQuare Fusion - Examples of use

This directory contains examples of use for XQuare Fusion. The directory for each individual example generally contains:

  • a load.sql file, used to create the relational schema and insert relational data (if required). This file can be loaded using your favorite RDBMS command-line utility. This script is written using the most portable syntax, however if an alternate script is not provided for your RDBMS (check for load_rdbms.sql files) you may need to adjust it by yourself.
  • In the case of examples using Java code (XML/DBC API and insertion with generators), the source code itself, the Ant build.xml file used to compile the example, plus any support file required to run the example.

Note that all the source files have been compiled using Ant (version 1.5.3). Any other build tool should work as well, but you will need to write your own build file.

The command-line examples given below assume that the XQuare Fusion command-line tool has been properly configured, as detailed in the installation guide.

Note
1. The commands will print the query results on the standard output.
2. The SQL instructions present in the load.sql file must have been previously executed in order to create the required relational structures and data.
ExampleDescription
extractorThis directory contains the configuration file main.xml of the XQuare Fusion for executing the relational use cases specified by the W3C.
main.xml defines 3 differents wrappers WSQL1.cfg, WSQL2.cfg and WSQL3.cfg, each one being for now an SQL Wrapper running above the XQuare Fusion.Within each SQL Wrapper configuration file is defined the underlying JDBC connection parameters with the tags <user>/<password>/<url>.
You should adapt/modify these parameters to your local environment as well as the "name" attribute of the <schema> element. It also contains a set of XQuery files (suffixed by .xqy) adapted from the relational use cases specified by the W3C.
Each query can be executed using the following command:
xqfusion main.xml q4-xx.xqy
mixedThis directory contains the configuration file main.xml of the XQuare Fusion for executing the relational use cases specified by the W3C.
main.xml defines 2 differents wrappers WSQL1.cfg and WSQL2.cfg , each one being for now an SQL Wrapper running above the XQuare Fusion. Some data is contained in a document named bids.xml.Within each SQL Wrapper configuration file is defined the underlying JDBC connection parameters with the tags <user>/<password>/<url>.
You should adapt/modify these parameters to your local environment as well as the "name" attribute of the <schema> element. It also contains a set of XQuery files (suffixed by .xqy) adapted from the relational use cases specified by the W3C.
Each query can be executed using the following command:
xqfusion main.xml q4-xx.xqy
xqueryThis directory contains the configuration file main.xml of the XQuare Fusion for executing the relational use cases specified by the W3C.
main.xml does not define any wrapper. Data is contained in three documents named users.xml, items.xml and bids.xml. Within each SQL Wrapper configuration file is defined the underlying JDBC connection parameters with the tags <user>/<password>/<url>.
You should adapt/modify these parameters to your local environment as well as the "name" attribute of the <schema> element. It also contains a set of XQuery files (suffixed by .xqy) adapted from the relational use cases specified by the W3C.
Each query can be executed using the following command:
xqfusion main.xml q4-xx.xqy
by Odonata