anchor.diff:          "typeExpression": "serial",
           "charsetName": null,
           "length": 10,
  -        "scale", 0,
  +        "scale": 0,
           "position": 1,
           "optional": false,
           "autoIncremented": true,
  
positive.code:         "typeExpression": "int4",
          "charsetName": null,
          "length": 10,
          "scale", 0,
          "position": 2,
          "optional": true,
          "autoIncremented": false,
  
negative.code: INSERT INTO DEBEZIUM_SIGNALS (ID, TYPE, DATA) VALUES ('1', 'schema-changes', <json-payload-string>);
  ```
  
  == Vitess SET support
  
  The Vitess team improved the `SET` data type support in the VStream API as part of Vitess 9.0.
  This improvement has lead to the `SET` data type now being supported by the Debezium Vitess connector.
  This data type will be emitted as an `EnumSet` that will now contain all the permissible values of the column's `SET` definition.
  
  == Other Features and Fixes
  
  Besides the Signal Table and Vitess SET support, a few other improvements and fixes found their way into this release.
  
  * The Debezium connector for Oracle now uses the LogMiner-based capturing implementation by default.
  In order to use the XStream-based implementation, the `database.connection.adapter` option must be explicitly set to `xstream` (https://issues.redhat.com/browse/DBZ-3241[DBZ-3241]).
  