Model and Translator Properties

null

When false, directs the importer to drop the source catalog/schema from the object name, so that the fully qualified name will be in the form of <model name>.<table name>

Note: When false this may lead to objects with duplicate names when importing from multiple schemas, which results in an exception.  This option does not affect the name in source property.

true to import primary and foreign keys

Note: Foreign keys to tables that are not imported will be ignored.

true to import approximate index information.

See DatabaseMetaData.getIndexInfo [1]

true to import procedures and procedure columns.

Note that it is not always possible to import procedure result set columns due to database limitations. It is also not currently possible to import overloaded procedures.

true to convert unsigned types to the next widest type. For example SQL Server reports tinyint as an unsigned type.

With this option enabled, tinyint would be imported as a short instead of a byte.

true will allow the import of overloaded procedures (which will normally result in a duplicate procedure error) by using the unique procedure specific name as the service name.

This option will only work with JDBC 4.0 compatible drivers that report specific names.

 false

true will use any non-null/non-empty catalog name as part of the name in source, e.g. "catalog"."schema"."table"."column", and in the service runtime name if useFullSchemaName is also true.

false will not use the catalog name in either the name in source or the service runtime name. Should be set to false for sources that do not fully support a catalog concept, but return a non-null catalog name in their metadata - such as HSQL.

true will use name qualification for both the service name and name in source as dictated by the useCatalogName and useFullSchemaName properties.  

Set to false to disable all qualification for both the service name and the name in source, which effectively ignores the useCatalogName and useFullSchemaName properties.  

Note: When false this may lead to objects with duplicate names when importing from multiple schemas, which results in an exception.

 true

true will use the maximum cardinality returned from DatabaseMetaData.getIndexInfo. importKeys or importIndexes needs to be enabled for this setting to have an effect.

This allows for better stats gathering from sources that don’t support returning a statistical index.

true will use database dependent logic to determine the cardinality if none is determined.

Not yet supported by all database types – currently only supported by Oracle and MySQL.

true will import RowId columns as varbinary values.

The base supported version or the version derived from the DatabaseMetadata.getDatabaseProductVersion string. Automatic detection requires a Connection.

If there are circumstances where you are getting an exception from capabilities being unavailable (most likely due to an issue obtaining a Connection), then set DatabaseVersion property.

Use the JDBCExecutionFactory.usesDatabaseVersion() method to control whether your translator requires a connection to determine capabilities.

MessageFormat string to be used if UseCommentsInSourceQuery is enabled.

Available properties:

 0 - session id string

 1 - parent request id string

 2 - request part id string

 3 - execution count id string

4 - user name string

5 - VDB name string

6 - VDB version integer

7 - is transactional Boolean

Struct retrieval mode can be one of

OBJECT - getObject value returned

COPY - returned as a SerialStruct

ARRAY - returned as an Array

 OBJECT