DDXQDataSource and DDXQJDBCConnection Properties
The class name of the DataDirect XQuery XQDataSource implementation is:
com.ddtek.xquery.xqj.DDXQDataSource
It provides properties that allow you to configure most DataDirect XQuery settings and data source connections. Table 6-1 lists the properties supported by the DDXQDataSource class, DataDirect XQuery’s XQDataSource implementation, and describes each property.
The following class provides additional properties for configuring connections to multiple databases:
com.ddtek.xquery.xqj.DDXQJDBCConnection
See Table 6-2 for a list of the additional properties supported by the DDXQJDBCConnection class.
NOTE: All property names are case-insensitive. For example, password is the same as Password.
DDXQDataSource Properties
sql-extra-checks-trailing-spaces
sql-ignore-trailing-spaces
sql-ora10-use-binary-float-double
sql-order-by-on-values
sql-rewrite-algorithm
sql-rewrite-exists-into-count
sql-simple-convert-functions
sql-simple-string-functions
sql-sybase-temptable-index
sql-sybase-use-derived-tables
sql-unicode-strings
sql-varchar-castSee Option Declarations for a description of these option declarations.The value of this property is a semicolon-separated list of option declaration name=value pairs:name=value[;name=value]...For example:sql-unicode-strings=yes;sql-decimal-cast=10,5You also can specify a global option declaration for all XML and relational data sources using the Options property.NOTE: You can override this setting in the query.If specifying an option declaration for multiple databases, use the Options property of the DDXQJDBCConnection class.
- none (the default) – No mapping is performed. An error is raised if a character in a SQL identifier cannot be mapped to XML.
- partial – Characters in SQL identifiers that are not XML characters are escaped using an underscore character (_) followed by a lowercase x followed by the character’s Unicode representation in hexadecimal format followed by an underscore character (_). For example, sales!forecast becomes sales_x0021_forecast.
- full – In addition to the escaping performed by partial, the character x of a SQL identifier that starts with "xml" (in any combination of upper and lowercase characters) is escaped. For example, XMLTable becomes _x0058_MLTable.
xquerytype="value"sqlType="value".Specifies which SQL type is used for columns when DataDirect XQuery creates temporary tables for query optimization.If you do not specify a value for this property, DataDirect XQuery uses the SQL/XML mappings to determine which SQL type to use for the columns of temporary tables; however, this can sometimes cause problems. For example, if your database table has a case-sensitive collation and the temporary table is created with a case-insensitive collation, an error is raised. In this case, use this property to specify that the temporary tables be created with a case-sensitive collation.A value forxqueryTypeis required and specifies one of the following values: boolean, byte, date, dateTime, decimal, double, float, hexBinary, int, integer, long, short, string, or time.A value forsqlTypeis required and determines the database type declaration that is appended to the column names when temporary tables are created. The specified data type must be supported by the database used to create the temporary tables.For example:xqueryType="string" sqlType="nvarchar(2000) collate SQL_Latin1_General_CP1_CS_AS"
- java.sql.Connection.TRANSACTION_READ_UNCOMMITTED –Locks are obtained on modifications to the database and held until end of transaction (EOT). Reading from the database does not involve any locking.
- java.sql.Connection.TRANSACTION_READ_COMMITTED – Locks are acquired for reading and modifying the database. Locks are released after reading, but locks on modified objects are held until EOT.
- java.sql.Connection.TRANSACTION_REPEATABLE_READ – Locks are obtained for reading and modifying the database. Locks on all modified objects are held until EOT. Locks obtained for reading data are held until EOT. Locks on non-modified access structures (such as indexes and hashing structures) are released after reading.
- java.sql.Connection.TRANSACTION_SERIALIZABLE – All data read or modified is locked until EOT. All access structures that are modified are locked until EOT. Access structures used by the query are locked until EOT.
- java.sql.Connection.TRANSACTION_NONE – Transactions are not supported.
- -1 – The default transaction isolation level is used, which is Read Committed.
The database to which you are connecting may not support all of these isolation levels. See Transaction Isolation Levels for details.NOTE: Once a connection is made, the transaction isolation level cannot be changed for that connection (XQConnection object).name=valuewhere value is either yes or no. For example:detect-XPST0005=no(spy_attribute=value[;spy_attribute=value]...)wherespy_attribute=valueis a DataDirect Spy attribute and a valid value for that attribute. The following example specifies that DataDirect Spy log all XQJ activity to a log file, including the content of SAX streams passed through XQJ.ds.setSpyAttributes("log=(file)/tmp/spy.log;
logSAX=yes")NOTE: When coding a path in a Java string on Windows, the backslash character (\) must be preceded by the Java escape character, which is also a backslash. The Spy parser also uses the backslash as an escape character, so four slashes must be used to specify a single backslash in the log path. For example:ds.setSpyAttributes("log=(file)C:\\\\temp\\\\spy.log;logSAX=yes")Once enabled. you can turn DataDirect Spy on and off at runtime using the setEnableLogging() method of the com.ddtek.xquery.xqj.ExtLogControl interface.See Logging XQJ Calls with DataDirect Spy™ for XQJ for instructions on using DataDirect Spy and a list of supported attributes.
DDXQJDBCConnection Properties
Table 6-2 lists the properties supported by the DDXQJDBCConnection class and describes each property (see Table 6-1 for a list of the properties supported by the DDXQDataSource class).
- sql-decimal-cast
- sql-extra-checks-trailing-spaces
- sql-ignore-trailing-spaces
- sql-ora10-use-binary-float-double
- sql-order-by-on-values
- sql-rewrite-algorithm
- sql-rewrite-exists-into-count
- sql-simple-convert-functions
- sql-simple-string-functions
- sql-sybase-temptable-index
- sql-sybase-use-derived-tables
- sql-unicode-strings
- sql-varchar-cast
See Option Declarations for a description of these option declarations.The value of this property is a semicolon-separated list of option declaration name=value pairs:name=value[;name=value]...For example:sql-unicode-literals=yes;sql-decimal-cast=10,5You also can specify a global option declaration for all XML and relational data sources using the Options property of the DDXQDataSource class.NOTE: You can override this setting in the query.If specifying an option declaration for a single database, use the JdbcOptions property of the DDXQDataSource class.
- none (the default) – No mapping is performed. An error is raised if a character in a SQL identifier cannot be mapped to XML.
- partial – Characters in SQL identifiers that are not XML characters are escaped using an underscore character (_) followed by a lowercase x followed by the character’s Unicode representation in hexadecimal format followed by an underscore character (_). For example, sales!forecast becomes sales_x0021_forecast.
- full – In addition to the escaping performed by partial, the character x of a SQL identifier that starts with "xml" (in any combination of upper and lowercase characters) is escaped. For example, XMLTable becomes _x0058_MLTable.
xquerytype="value"sqlType="value".Specifies which SQL type is used for columns when DataDirect XQuery creates temporary tables for query optimization.If you do not specify a value for this property, DataDirect XQuery uses the SQL/XML mappings to determine which SQL type to use for the columns of temporary tables; however, this can sometimes cause problems. For example, if your database table has a case-sensitive collation and the temporary table is created with a case-insensitive collation, an error is raised. In this case, use this property to specify that the temporary tables be created with a case-sensitive collation.A value forxqueryTypeis required and specifies one of the following values: boolean, byte, date, dateTime, decimal, double, float, hexBinary, int, integer, long, short, string, or time.A value forsqlTypeis required and determines the database type declaration that is appended to the column names when temporary tables are created. The specified data type must be supported by the database used to create the temporary tables.For example:xqueryType="string" sqlType="nvarchar(2000) collate SQL_Latin1_General_CP1_CS_AS"
- java.sql.Connection.TRANSACTION_READ_UNCOMMITTED – Locks are obtained on modifications to the database and held until end of transaction (EOT). Reading from the database does not involve any locking.
- java.sql.Connection.TRANSACTION_READ_COMMITTED – Locks are acquired for reading and modifying the database. Locks are released after reading, but locks on modified objects are held until EOT.
- java.sql.Connection.TRANSACTION_REPEATABLE_READ – Locks are obtained for reading and modifying the database. Locks on all modified objects are held until EOT. Locks obtained for reading data are held until EOT. Locks on non-modified access structures (such as indexes and hashing structures) are released after reading.
- java.sql.Connection.TRANSACTION_SERIALIZABLE – All data read or modified is locked until EOT. All access structures that are modified are locked until EOT. Access structures used by the query are locked until EOT.
- java.sql.Connection.TRANSACTION_NONE – Transactions are not supported.
- -1 – The default transaction isolation level is used, which is Read Committed.
The database to which you are connecting may not support all of these isolation levels. See Transaction Isolation Levels for details.NOTE: Once a connection is made, the transaction isolation level cannot be changed for that connection (XQConnection object).