Dr.Sum 5.5 Adapter Limitations

• Supported Types
• Common to all processing
• Read Table/View
• Execute Datalizer
• Write(VTB)
• Write(BulkInsert)
• Write(DataLoader)
• Write(Update/Insert)
• Execute Select Query
• Execute Update Query
• Truncate

Supported Types

• Yes: Support.
• Limited: Support with limitations.
• No: Not support

Common to all processing

Specification Limits

• Use "/" for "Data delimiter" of Dr.Sum.
  If you set data delimiter as "-", reading data from a table containing date type columns is not possible.

Notes

• If a table is created by Write(update/insert) operation and Execute Select Query operation in the Designer, the table will not be displayed in the list of tables immediately. Also obtaining schema information is not possible. To solve the issue, please reopen the designer.

Read Table/View

Specification Limits

• OBJECT type is not supported.


• It is not possible to execute to a table with its name containing surrogate pair characters.


• It is not possible to execute to a table with a column containing surrogate pair characters.


• In case of TIME type and TIMESTAMP type, even if you set the precision to 4 or higher, the fractions below the fourth decimal place are truncated and then read.

Notes

• Error may occur due to timeout at the time of committing may occur when the processing time is long.In this case, global resources [Process timeout] or simply a longer processing time in seconds, "0" (ignoring the time-out), this error may be avoided by setting.

Execute Datalizer

Specification Limits

• Link definition is not supported.


• Set custom fields definition file does not support the criteria.


• In [Definition file name], you can specify the definition files below.
  • Definition files created in Dr.Sum Datalizer for Web
  • TYPE4 Definition files created in Excel Plugin of Dr.Sum Datalizer
    • You cannot specify if you are only using Dr.Sum Datalizer for Excel or Dr.Sum Datalizer Professional for Excel. For details on available Dr.Sum Datalizer, please refer to "Operating environment".
• For multi-aggregate can be specified [Download file type] is [EXCEL], [PDF].


• [Definition file name] definition file name exists with the same name, Datalizer reads the definition file is defined in the top.


• If items with the same names exist more than one in [Column], [Row], or [Summary] of [Items for adjusting aggregation condition], the aggregation result may not appear as you've configured.

Write(VTB)

Specification limits

• If selecting [Continue] when [Action upon error], you cannot acquire information regarding to the record that error occurred.
  Refer to import.log of Dr.Sum server.

Write(BulkInsert)

Specification Limits

• A NULL value and an empty string are distinguishly written if a value is a VARCHAR type.
  If a value is in other types, it is written as NULL.


• When the script transaction attribute is enabled, or if there is non-committed data which has changed in the Execute Update Query operation into Dr.Sum exists in the transaction icon (BEGIN - COMMIT), if you try to write in the same table by the Write(BulkInsert) operation, a table lock error will occur.


• In PSP, errors may occur if other processing that executes loading or writing to the same tables as the specified tables in [Table name] already exist.


• Distributor-type insertion sequence, the transition is made import position. But circulation is set to ON transition of the first table from the table import position last become even does not take an error.


• It is not possible to execute to a table with its name containing surrogate pair characters.


• It is not possible to execute to a table with a column containing surrogate pair characters.


• When the precision is set to 4 or higher in TIME type and TIMESTAMP type, the fractions below the fourth decimal place are filled with 0 and written.

Notes

• Error may occur due to timeout at the time of committing may occur when the processing time is long.In this case, global resources [Process timeout] or simply a longer processing time in seconds, "0" (ignoring the time-out), this error may be avoided by setting.


• When a value that includes a decimal is written to TIME type, TIMESTAMP type, or INTERVAL type, any digit in a decimal place larger than the specified precision will be truncated.
  Example: When the specified precision is "1", "10:10:10.123" will be "10:10:10.1".

Write(DataLoader)

Specification Limits

• OBJECT type is not supported.


• A column or a compound key with NOT NULL UNIQUE restriction can be selected as a key.


• If the in-memory table, in which the in-memory mode is "Direct" is written to, a column not only with NOT NULL UNIQUE restriction, but also with NOT NULL restriction can be specified as a key. To specify the column to be used as a key, directly enter the column name in [Key Column Name] list.


• An error occurs if the column or the compound key that meets none of the above conditions is specified.


• Multiple columns cannot be used as a key.


• NULL values are written to an empty distinction.


• Can not participate in the transaction.


• When the script transaction attribute is enabled, or if there is non-committed data which has changed in the Execute Update Query operation into Dr.Sum exists in the transaction icon (BEGIN - COMMIT), if you try to write in the same table by the Write(DataLoader) operation, a table lock error will occur.


• In PSP, errors may occur if other processing that executes loading or writing to the same tables as the specified tables in [Table name] already exist.


• If an error occurs in Write(DataLoader) operation, UPDATE and INSERT will not be executed.


• It is not possible to write in a distributor.


• It is not possible to execute to a table with its name containing surrogate pair characters.


• It is not possible to execute to a table with a column containing surrogate pair characters.


• When the precision is set to 4 or higher in TIME type and TIMESTAMP type, the fractions below the fourth decimal place are filled with 0 and written.

Notes

• Error may occur due to timeout at the time of committing may occur when the processing time is long.In this case, global resources [Process timeout] or simply a longer processing time in seconds, "0" (ignoring the time-out), this error may be avoided by setting.


• When a value that includes a decimal is written to TIME type, TIMESTAMP type, or INTERVAL type, any digit in a decimal place larger than the specified precision will be truncated.
  Example: When the specified precision is "1", "10:10:10.123" will be "10:10:10.1".

Write(Update/Insert)

Specification Limits

• OBJECT type is not supported.


• NULL values are written to an empty distinction.


• When you insert data into the order-type distributor, the number exceeds the upper limit of the server group table is an error there. Import position transition in that process does not insert.


• Table creation function
  When [Create table] is checked, the specification limits are as follows.
  • The column in which [Key] of [Schema definition] is checked is defined as a unique key, [Allow null] setting is ignored.
  • Writing fails when the creating or deleting table fails.
  • Creating or deleting table operates out of the transaction.
  • The setting of the precision of REAL type and DATE type is ignored.
  • Precision of VARCHAR can only be specified as 1 to 225.If a number outside that range is specified, or nothing is specified, type will be defined without specifying precision.
  • Precision of NUMERIC can only be specified as 1 to 33. If you specify a value outside the range 33 to define the empty set to 0.
  • The decimal place of NUMERIC can only be specified as 0 to 33. Outside the range that is specified or empty, and then defined with a 0.
  • NUMERIC 0 or empty if both digits and fractional digits, and do not define the number of digits and fractional digits.
  • The setting of decimal place is ignored for types other than NUMERIC.
  • The precision that can be specified in TIME type, TIMESTAMP type and INTERVAL type is more than 0 and less than 6. When you specify a number beyond this range, error occurs.
• It is not possible to execute to a table with its name containing surrogate pair characters.


• It is not possible to execute to a table with a column containing surrogate pair characters.


• When the precision is set to 4 or higher in TIME type and TIMESTAMP type, the fractions below the fourth decimal place are filled with 0 and written.

Notes

• Error may occur due to timeout at the time of committing may occur when the processing time is long.In this case, global resources [Process timeout] or simply a longer processing time in seconds, "0" (ignoring the time-out), this error may be avoided by setting.


• When a value that includes a decimal is written to TIME type, TIMESTAMP type, or INTERVAL type, any digit in a decimal place larger than the specified precision will be truncated.
  Example: When the specified precision is "1", "10:10:10.123" will be "10:10:10.1".

Execute Select Query

Specification Limits

• OBJECT type is not supported.


• About inner join (INNER JOIN)
  • Dr.Sum Due to the limitations of the condition and either the tables are KEY PRIMARY KEY must be.
• About outer join (OUTER JOIN)
  • Joins in FROM Clause
    • Due to the limitations of Dr.Sum, ON clause can only be specified in the table join conditions, you can not find mention of the condition.
    • Dr.Sum Due to the limitations of the outer join table is either a key join condition must be PRIMARY KEY.
  • Combining WHERE clause
    • Dr.Sum Due to the limitations of the outer join table if the condition is "=", "*=", "=*" join either one or the other must be the PRIMARY KEY key.
  • Combining a composite key
    • SQL Wizard , the binding does not support composite keys. [SQL statement] Please specify directly.
• It is not possible to execute to a table with its name containing surrogate pair characters.


• It is not possible to execute to a table with a column containing surrogate pair characters.


• In case of TIME type and TIMESTAMP type, even if you set the precision to 4 or higher, the fractions below the fourth decimal place are truncated and then read.

Notes

• Error may occur due to timeout at the time of committing may occur when the processing time is long.In this case, global resources [Process timeout] or simply a longer processing time in seconds, "0" (ignoring the time-out), this error may be avoided by setting.

Execute Update Query

Specification Limits

• OBJECT type is not supported.


• NULL values are written to an empty distinction.


• INSERT when inserting data into sentences using an ordinal type distributor, the number exceeds the upper limit of the server group table is an error there. Import position transition in that process does not insert.


• It is not possible to execute to a table with its name containing surrogate pair characters.


• It is not possible to execute to a table with a column containing surrogate pair characters.


• When the precision is set to 4 or higher in TIME type and TIMESTAMP type, the fractions below the fourth decimal place are filled with 0 and written.

Notes

• Error may occur due to timeout at the time of committing may occur when the processing time is long.In this case, global resources [Process timeout] or simply a longer processing time in seconds, "0" (ignoring the time-out), this error may be avoided by setting.


• When a value that includes a decimal is written to TIME type, TIMESTAMP type, or INTERVAL type, any digit in a decimal place larger than the specified precision will be truncated.
  Example: When the specified precision is "1", "10:10:10.123" will be "10:10:10.1".

Truncate

Specification Limits

• It is not possible to execute to a table with its name containing surrogate pair characters.


• It is not possible to execute to a table with a column containing surrogate pair characters.

Notes

• Error may occur due to timeout at the time of committing may occur when the processing time is long.In this case, global resources [Process timeout] or simply a longer processing time in seconds, "0" (ignoring the time-out), this error may be avoided by setting.