Release 4.2.1

Enhancements

• Data source management
  • When the number of data sources is large,time of synchronization is quickly.
  • Created or deleted databases in the structural tree support synchronous refresh.
  • Structural tree added data source connection state.
  • Logging into the database opens the corresponding sql console.
    

Bug fixed

• SQL execution
  • The DBMS output cannot be printed for versions earlier than OceanBase4.0.
  • Slow generation of DML statements when editing result sets.
• Import and export
  • The imported or exported objects are not displayed in the task details.
• PL debug
  • PL debugging occasionally fails to connect to the database when OceanBase is deployed on multiple nodes.
  • OceanBaseOracle schema Gets database connection error while debugging anonymous block in lowercase schema.
• Data source management
  • The flashback statement against the index generated by the Recycle Bin module executes an error.
  • The session management interface cannot display the SQL that is being executed by the session.
  • A null pointer exception is raised when there are empty lines or columns in the template file when importing connections in batches.
  • When you create a data source using older browsers, you cannot select a data source type by dropping down.
  • Databases under other tenants are displayed when the database is synchronized.
  • Updating the data source did not synchronize the database.
• Data desensitization
  • When the OceanBaseMySQL mode is case-sensitive, sensitive columns cannot be case-sensitive.
  • Data desensitization does not take effect for result set export.
• Task management
  • After the work order is submitted, the status of the work order is "queued" for a long time and no error is reported.
• Third-party integration
  • The ID of an external approval ticket is also attempted when the approval flow does not contain an external approval node.
• SQL-Check
  • OceanBaseOracle mode cannot detect the presence of a table or column comment.
• Result set
  • The column pattern is not displayed correctly when filtering the result set.
• SQL console
  • The SQL window will delete the first matching keyword after the search.
• Security hardening
  • Resolve SSRF attacks that may occur during third-party integration.

Release 4.2.0

If upgrading from an earlier version to ODC 4.2.0, be sure to read the upgrade Notes!

Features

• Change control
  • Support project-based control.
  • Support SQL check.
  • Supports automatic generation of rollback scripts corresponding to update/delete statements.
• Security compliance
  • Support dynamic desensitization.
  • Enrich operation records.
• Data lifecycle
  • Support data cleanup.
  • Support data archiving.
• Executive analysis
  • Supports full-link diagnosis from the perspective of SQL execution.
    

Enhancements

• PL lifecycle
  • PL debug input parameter interaction comprehensive upgrade, support to specify the current time as input parameter.
  • PL supports viewing the contents of sys_refcursor return values.
• SQL Console
  • The object tree shows all databases with permissions.
  • Support for switching databases.
• SQL execution
  • The result set displays the date value according to the nls_date_format parameter value of the queried session.
  • Solve floating-point data display problems (add 0 before the decimal point when less than 1).
  • Add right-click paste function to SQL window (Note: need to operate in a secure network access environment /https, otherwise clipboard capability will be disabled).
• Data generation and migration
  • The import function is compatible with the external tool PL/SQL Developer.
  • In OceanBase MySQL mode, SEQUENCE objects can be exported.
• Database object
  • In OceanBase Oracle mode, solve the problem that the foreign key is disabled in the table object editing page.
  • Add the NULL option to the field default value when creating a table.
• Access authority
  • Support the integration of Polystone tower account identification administrator identity.
• System integration
  • Productization of external approval integration, including approval integration, SQL audit integration, SSO integration.
• Desktop version
  • The ODC client version is compatible with the Linux desktop version and supports the Ubuntu20 OS.
• Other experience improvements
  • Login locked Display retry time.
  • Front-end error handling optimization, parsing results error scenarios show more information.
    

Bug fixed

• Database change
  • When a database change task contains time-consuming statements, the corresponding SQL execution is not canceled upon termination.
  • In multi-node deployment, database change download query results may fail.
• SQL execution
  • In OceanBase Oracle mode, when the table name is a keyword, the automatic completion of select with a name is unavailable.
  • When formatting, a space is automatically added in the middle of '=>'.
  • In OceanBase Oracle mode, the CREATE USER xxx IDENTIFIED BY ""; delimits fails.
  • Query error when binary number column contains Nan or Inf.
• PL object
  • Parsing failed when the program contains a mod b compound expression.
• Table
  • Failed to upload a large object, resulting in poor readability.
  • In OceanBase Oracle mode, editing table data cannot generate UPDATE statements.
• Desktop
  • Later versions of Java 9 does not provide the corresponding error information, indicating that the Java process exits unexpectedly.
  • Start the desktop for a long time without response.
• Security hardening
  • Fix OSS file traversal risk.
    

Upgrade notes

• Data source
  • The connection configuration concept is adjusted to the data source.
  • ODC V4.2.0 does not support new ODP Sharding data sources, and will be restored in subsequent versions.
  • Personal connections migrate into personal space and exist in the form of data sources.
  • Public connections migrate to the team space in the form of data sources.
  • In the original public connection, only read/write accounts are retained after the upgrade.
• User rights
  • Disable private_connection/apply_connection role. The privileges of private_connection/apply_connection role referred by users who have upgraded to ODC V4.2.0 are no longer valid.
  • Offline the resource group.
  • Offline connection access permission, ODC V4.2.0 through the project management to achieve access control to the database.
• System setting
  • Offline in ODC V4.2.0.
• Ticket module
  • Historical tickets are only allowed to view the work orders initiated by the user.
• Partitioning plan
  • It is not supported in ODC V4.2.0 and is restored in later versions.
  • After upgrading to ODC V4.2.0, the historical partition plan task will stop running.
• SQL plan
  • After upgrading to ODC V4.2.0, the historical SQL plan tasks will stop running.
• Task flow
  • The function module is offline in ODC V4.2.0, and the risk level module has been launched to achieve the corresponding effect.
• Data desensitization
  • This function has been upgraded in ODC V4.2.0, and the historical data desensitization configuration no longer takes effect.
• Bastion machine integration
  • This function is temporarily unavailable in ODC V4.2.0 and will be restored in later versions.
• History conversation
  • Offline history session, ODC V4.2.0 will save the SQL window usage status by default.