View Entry

DB2 SQL Extension Toolkit - Release Notes 

11 days ago

v1.3

November 5, 2019

  • Support for NVARCHAR/NCHAR functions added.
  • README updated with the minimum CLPPLUS version.
  • Fixed bug where either parameter of days_between is NULL.
  • Fixed bug where renaming extracted directory leads to failure of registration.

v1.2

September 6, 2019


  • Migrated setup script from shell to Python for better user experience.
  • Schema as an option is provided to register the UDXes.
  • SSL connection using a DSN is now supported.
  • Architecture check has been added which will notify the user if incorrect platform packages are used
  • Added graceful error message for erroneous exit.
  • Argument validation wherever applicable.

v1.1

August 13, 2019


  • Prefix DBTK_ has been removed from the functions' names.
  • Max number of arguments accepted changed.
  • Handled case where password contains special characters.
  • Included README with the package.
  • The project is also deleted now from the file-system after dropping all the UDXes while cleanup.

v1.0

July 26, 2019

Below functions are implemented in this release,
Note : All the functions are registered with prefixed with "DBTK_<function name>"

Array Functions

XML Functions

Regular Expression Functions

Text Analytics Functions

Data Transformation Functions

Date and Time Functions

Hashing Functions

ARRAY

ISVALIDXML

REGEXP_EXTRACT_ALL

WORD_DIFF

COMPRESS

DAYS_BETWEEN

HASH_NVARCHAR

ADD_ELEMENT

ISXML

REGEXP_EXTRACT_ALL_SP

WORD_FIND

DECOMPRESS

 

MT_RANDOM

ARRAY_COMBINE

XMLATTRIBUTES

REGEXP_EXTRACT_SP

WORD_KEY

DECRYPT

 

 

ARRAY_CONCAT

XMLCONCAT

REGEXP_REPLACE_SP

WORD_KEY_DIFF

ENCRYPT

 

 

ARRAY_COUNT

XMLELEMENT

REGEXP_VERSION

WORD_KEY_TOCHAR

FPE_DECRYPT

 

 

ARRAY_SPLIT

XMLEXISTSNODE

 

WORD_STEM

FPE_ENCRYPT

 

 

ARRAY_TYPE

XMLEXTRACT

 

 

UUENCODE

 

 

ELEMENT_TYPE

XMLEXTRACTVALUE

 

 

UUDECODE

 

 

ELEMENT_NAME

XMPARSE

 

 

CRYPTO_VERSION

 

 

REPLACE_ELEMENT

XMLROOT

 

 

 

 

 

DELETE_ELEMENT

XMLSERIALIZE

 

 

 

 

 

GET_VALUE_DATE

XMLUPDATE

 

 

 

 

 

GET_VALUE_DOUBLE

 

 

 

 

 

 

GET_VALUE_INT

 

 

 

 

 

 

GET_VALUE_TIME

 

 

 

 

 

 

GET_VALUE_TIMESTAMP

 

 

 

 

 

 

GET_VALUE_TIMETZ

 

 

 

 

 

 

GET_VALUE_VARCHAR

 

 

 

 

 

 

COLLECTION

 

 

 

 

 

 



Known Issues:

  • For ARRAY_COMBINE function, more than one character delimiter does not work.
  • ENCRYPT and COMPRESS results may vary as compared to PDA. If you encrypt a string using ENCRYPT function and use DECRYPT function on result of formerreturns original string. Similar for COMPRESS and DECOMPRESS functions. Eg. VALUES(DECRYPT(ENCRYPT('string')) = 'string'

Best Practices:

  • NVARCHAR is internally handled in VARCHAR in db2. Thus, registering the functions with the VARCHAR variant only, which will internally handle NVARCHAR as well.
  • ARRAY objects are fit in VARCHAR column of the table. It is the user's responsibility to allocate appropriate memory in VARCHAR. Eg. VARCHAR(100) might give error while adding multiple BIGINT values. However, changing it to VARCHAR(10000) will solve the issue.
  • Since BYTEINT is converted to SMALLINT in db2, ARRAY(1) gives an error for such a query. The user is advised to use ARRAY(2), as BYTEINT values are handled in SMALLINT.
  • User needs to use functions with schema name under which they are registered. Schema will be the user name with which the package was installed.
  • Output representation is different for DOUBLE/BOOLEAN in Db2 compared to PDA. So, you might observe output difference in case you are using DOUBLE/BOOLEAN data types with the functions.
  • If your workload/query involves "NCHAR", "NVARCHAR" data then your system must be set with appropriate STRING_UNITS configurations.

Statistics

0 Favorited
8 Views
0 Files
0 Shares
0 Downloads