Notice
- Before you upgrade OceanBase Developer Center (ODC) from a version earlier than V4.2.0 to V4.3.2-BP, you must read through the Considerations section in this topic.
- Before you use ODC V4.3.2-BP, familiarize yourself with the descriptions in the Limitations topic.
Considerations
Data sources
In ODC V4.2.0 and later, the concept of connection configuration is replaced with data source.
In ODC V4.2.0 and later, private connections are migrated to the individual workspace and exist as data sources.
In ODC V4.2.0 and later, public connections are migrated to the team workspace and exist as data sources.
In ODC V4.2.0 and later, for the read-only and read/write accounts in original public connections, only the read/write accounts are retained after the upgrade.
User permissions
Starting from ODC V4.2.0, the
private_connectionandapply_connectionroles are unavailable. In other words, the permissions of the two roles referenced by users no longer take effect after the upgrade to ODC V4.2.x.Starting from ODC V4.2.0, the resource group feature is obsolete.
Starting from ODC V4.2.0, connection access permissions are obsolete. In ODC V4.2.x, database access control is implemented through project management.
System settings
- Starting from ODC V4.2.0, this feature is obsolete.
Ticket module
- Tickets initiated in versions earlier than ODC V4.2.0 can be viewed only on the Initiated by Me tab.
Partitioning plans
- This feature is upgraded in ODC V4.2.0. After the upgrade to ODC V4.2.x, historical partitioning plans created in versions earlier than V4.2.0 will stop running.
SQL plans
- This feature is upgraded in ODC V4.2.0. After the upgrade to ODC V4.2.x, historical SQL plans created in versions earlier than V4.2.0 will stop running.
Task process
- Starting from ODC V4.2.0, this feature is obsolete. ODC V4.2.x provides the risk level module for equivalent effects.
Data desensitization
- This feature is upgraded in ODC V4.2.0. After the upgrade to ODC V4.2.x, the data desensitization configurations created in versions earlier than V4.2.0 no longer take effect.
Bastion host integration
- In ODC V4.2.2, account integration and automatic data source configuration are supported. At present, SQL approval integration is not supported and will be supported in later versions.
Session history
- Starting from ODC V4.2.0, this feature is obsolete. In ODC V4.2.x, the usage status of an SQL window is saved by default.
ODC V4.3.2-BP
The OceanBase Developer Center (ODC) V4.3.2 release in October primarily focuses on bug fixes.
Version information
Current version: V4.3.2-BP
Previous version: V4.3.2
Release date: October 30, 2024
Supported upgrade path: You can directly upgrade ODC V2.0.0 and later to this version.
Bug fixes
- Fixed an issue where environment labels in projects were not updated after modifying them in data sources.
- Fixed an error when opening the SQL console after adding custom environment labels to a data source.
- Fixed a PL debugging error that occurred when there were both deleted and non-deleted databases with the same name under the same data source.
- Fixed an issue where the specified condition matching strategy in data archiving did not take effect.
- Fixed a timeout error during archiving in OBOracle mode.
- Fixed an issue where archiving failed due to inconsistent field order between source and target in OBMySQL mode.
- Fixed the overly narrow right-click menu in the object tree.
ODC V4.3.2
OceanBase Developer Center (ODC) V4.3.2 released in September 2024 enhances the following features:
Support for logical databases: ODC V4.3.2 introduces new logical database features to provide a quick, reliable, and easy-to-use change basis for database and table sharding. The new features include logical database configuration, access privilege management, logical table obtaining and creation, and execution of data definition language (DDL) changes.
Archive link extension: ODC V4.3.2 adds two archive links to support archiving data from an Oracle database to an Oracle tenant of OceanBase Database and from a PostgreSQL database to a MySQL tenant of OceanBase Database, on the basis of the archive link supported in ODC V4.3.1 from a MySQL database to a MySQL tenant of OceanBase Database.
SQL development and data source management optimization: ODC V4.3.2 improves the usability of the SQL development page, data sources, and forms and optimizes more than 10 features such as the location key, resource tree object, and SQL execution result.
For more information, see the “Feature updates” section.
Version information
Current version: V4.3.2
Previous version: V4.3.1-BP
Release date: September 26, 2024
Supported upgrade path: You can directly upgrade ODC V2.0.0 and later to this version.
Feature updates
SQL check
- ODC V4.3.2 supports a specification for checking rows affected in MySQL tenants of OceanBase Database and in MySQL data sources, so as to restrict the execution of large SQL-based changes and ensure business stability.
Bug fixes
Data objects
Fixed the issue where an error is reported when the system executes the formatted SQL statements generated for columns that contain large object (LOB) fields after a file upload.
Fixed the issue where the precision of TINYINT data is incorrect in MySQL mode.
Fixed the issue where a column of the Character Large Object (CLOB) or Binary Large Object (BLOB) data type whose value is NULL cannot be edited on the GUI.
Change control
- Fixed the issue where pages cannot be scrolled when too many risk identification rules are specified.
Import and export
Fixed the issue where native MySOL data fails to be exported by using Client ODC on a Windows system.
Fixed the issue where an error is reported when the type of the exported table is BigDecimal.
Fixed the issue where the result set export fails when the
*orNVLfunction is used in SQL statements.Fixed the issue where the result set export fails when the table contains SDO_GEOMETRY data.
Data archiving
Fixed the issue where the number of scan records displayed in the details of executed archiving tasks is not accurate.
Fixed the issue where the privileges of a database administrator (DBA) are required for archiving the data of Oracle tenants of OceanBase Database.
Data sources
- Fixed the issue where a test can still be successful even though an Oracle tenant is selected as the source
systenant of OceanBase Database to be connected.
- Fixed the issue where a test can still be successful even though an Oracle tenant is selected as the source
Others
Fixed the issue where single sign-on (SSO) may fail in the environment with a load balancing service deployed.
Fixed the issue where the startup parameter
ODC_APP_EXTRA_ARGSis invalid.