This article describes the principal changes of MySQL Component.
If you need further information, please consult the full changelog.
Component download section can be found at this page.
Stambia DI is a flexible and agile solution. It can be quickly adapted to your needs.
If you have any question, any feature request or any issue, do not hesitate to contact us.
This article is dedicated to Stambia DI 2020 (S20.x.x) or higher.
Change Data Capture (CDC)
Multiple improvements have been performed to homogenize the usage of Change Data Capture (CDC) in the various Components.
Parameters have been homogenized, so that all Templates should now have the same CDC Parameters, with the same support of features.
Multiple fixes have also been performed to correct CDC issues. Refer to the changelog for the exact list of changes.
Datatypes and creation mask
Some datatypes such as BINARY, JSON, TINYTEXT and VARBINARY have been added in MySQL Component, they were missing.
Moreover, YEAR and BIT datatypes creation masks have also been fixed.
The complete changelog with the list of improvements and fixed issues can be found at the following location.
Missing MEDIUMTEXT datatype
MEDIUMTEXT datatype has been added in MySQL Component, it was missing.
JDBC Drivers classes and URLs
- Stambia DI Designer 2020 (S20.2.0) or higher
Stambia DI Designer 20.2.0 introduces an improvement which allows Components and Modules definition to provide themselves the proper JDBC drivers classes and URLs, for the connection wizard to automatically adapt depending on the Module selected.
This Component has therefore been updated to take into account this improvement and provide the necessary JDBC drivers classes and URLs information.
Creation of columns with auto increment fixed
MySQL requires that a column defined as "auto increment" is also set as primary key.
If both conditions are not met the create table statement will fail.
From now, when creating such columns in MySQL, such as when using Replicator or Automation Templates, autoincrement columns will be properly created and defined as primary key to avoid issues with table creation.