Tonic Structural release notes

v721 - v728
v721 - v728
Removed
February 24, 2023

As of V724, the AI Synthesizer generator is by default not available. To enable the AI Synthesizer generator, set the environment variable TONIC_NN_GENERATOR_ENABLED to true. If the AI Synthesizer generator is assigned in a table, but the environment variable is false, then data generation fails.

During subset processing, when Tonic encounters a circular dependency, to break the circle, it nullifies the values of one of the foreign key columns. By default, it nullifies all of the foreign key column values. A new environment variable, TONIC_SUBSETTING_AGGRESSIVELY_NULL_CYCLICAL_FKS, controls the behavior. By default, the value is true. If you set the value to false, then Tonic only nullifies foreign key values that do not exist as primary key values in the other table.

Fixed an issue where authentication using Azure SSO failed if the user was a member of a large number of IdP groups.

Improved detection during sensitivity scans of columns that contain birth dates.

MongoDB

  • Fixed an issue where adding a new null type field to the data caused data generation to fail.

Oracle

  • Fixed an issue where data generation returned the following error: Specified argument was out of the range of valid values. (Parameter 'minSize').

PostgreSQL

  • Fixed an issue where tables with generated columns, but no generator assignments, were not correctly copied to the destination database.
  • Improved handling and messaging for connection timeouts.

Snowflake

  • Fixed an issue where retrying a connection multiple times returned an incorrect error.

SQL Server

  • Fixed issues where users could not configure data generation for tables that contained hierarchyid columns.
  • Fixed an issue that prevented Preserve Destination from being used on schema-bound tables.
  • Fixed an issue that prevented Incremental and Preserve Destination table modes on memory-optimized tables.
  • Fixed an issue where column attributes such as the nullability of a column were not correctly reflected in the destination database.
  • Fixed an issue where schema binding was not maintained in the destination database.