Restrictions when working with the LookupDatabaseTable method - Connect_CDC - connect_cdc_mimix_share - 5.8

Connect CDC System Reference Guide

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (MIMIX Share)
Version
5.8
Language
English
Product name
Connect CDC
Title
Connect CDC System Reference Guide
Copyright
2024
First publish date
2003
ft:lastEdition
2024-02-12
ft:lastPublication
2024-02-12T15:11:59.486869

Keep in mind the following when working with the LookupDatabaseTable method:

  • When the kernel is loaded, the lookup keys and values are read into memory from the lookup table. The values in these columns are trimmed if any of these columns have a datatype of CHARACTER.

Note: This is not done for the VARCHAR SQL datatype.
  • Since the key/value pairs used in the method are loaded from an SQL table when the model is loaded, the kernel needs to have available the specific table name and column names in the SQL table in order to load it. This means that when the LookupDatabaseTable is coded in an expression, these identifiers must be literals so that the kernel can identify the specific names. The identifiers can not be variables.

  • You should not code an invocation of this method in a procedure. This is not supported because a procedure is a "model-wide" object and is not associated with a specified server as a result expression or as a gate (condition) expression is. The lookup table is an SQL table that has to be available in the source server context, because the kernel needs to connect to a source server, but a user procedure (a new compiled method created in the "Data Enhancement Methods" list) is not associated with any particular server.

  • All the rows in the SQL table specified in this method are loaded into kernel memory when a model is loaded. Therefore, this method is generally more suited to small, static tables in which one wants to do key/value look ups.

Note: Once loaded, the key/value pairs are fixed, static, even though the SQL table outside of the kernel may change; the kernel will not recognize any of these changes until it is started again and the table is reloaded.