Skip to content

Release 4.2.3

Choose a tag to compare

View all tags
@tonghan-gsh tonghan-gsh released this 26 Dec 06:40
· 1556 commits to main since this release
v4.2.3
09e4ec8
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Feature

  • Data source

    • Allow data sources to be bound to projects
    • Supports OceanBase Sharding MySQL data source
    • Supports cloning data sources
    • Supports displaying data source status in the object tree in the team space

  • Import and Export

    • Supports import and export of native MySQL data sources
    • SYS account configuration is no longer provided in the import and export task configuration page of OceanBase data source

  • Database object management

    • OceanBase MySQL and native MySQL mode supports GIS data types
    • White screen gives high-risk operation prompts when creating or deleting indexes

  • Project

    • Added 2 built-in project roles: security administrator, participant; security administrator is allowed to manage sensitive columns of the project and participate in approval, and participants are allowed to participate in approval
    • Allow users to apply for project permissions
    • Prohibit deletion of users who are assigned to any project with the DBA or project OWNER role

  • SQL-Check

    • Optimized SQL interception interaction
    • Added problem locating function to supports quick locating of specific problems in the original SQL

  • Connection session

    • Added an automatic reconnection mechanism to avoid errors and usability issues caused by session destruction when not used for a long time

  • Partition plan

    • Supports scheduled scheduling

  • SQL execution

    • SQL fragment supports a maximum content size of 65535
    • Supports Ctrl+Enter shortcut key to execute the current statement

  • Bastion integration

    • Supports SQL Check

  • DLM

    • Supports log viewing
    • Added three new task parameter configurations: query timeout, shard size, and shard strategy
    • Optimized the performance of MYSQL 5.6
    • Optimized the performance of OceanBase data cleaning

  • Full link trace

    • Supports exporting Jaeger-compatible JSON files
    • Optimized visual effects
    • Added list view of results, supporting search and sorting

  • Tickets

    • The project administrator can view all work orders under the project, and other roles can view the work orders they have approved

Enhancements

  • Improve SQL execution performance and reduce unnecessary time-consuming operations
  • Allow users to configure the maximum number of retries and account lockout time in the event of login failure
  • Only allow users to modify table data with primary key constraints, unique key constraints and rowid with a blank screen
  • Optimize the error text when synchronizing database errors
  • Upgrade obclient version to 2.2.4
  • Upgrade spring security version to 5.7.10
  • Upgrade hutool version to 5.8.23
  • Upgrade pf4j version to 3.10.0
  • Upgrade netty version to 4.1.94.FINAL

Bug fixed

  • Data source
    • Users can still create data sources when they leave the project and do not belong to any project or role
    • The "Execution Time" column in the database session in OceanBase MySQL and native MySQL modes is 0
    • Modification of the time output format through the session variable management function in OceanBase Oracle mode does not take effect in the SQL execution window
    • Lowercase schema cannot be connected in OceanBase Oracle mode
    • Unable to connect to MySQL data source built by percona branch
  • SQL execution
    • Error thrown during SQL execution without internationalization
    • SQL with dblink cannot be executed in the team space
    • The desc statement cannot be executed in the team space if security rules allow it
    • ORDER BY will be invalid when executing SELECT... ORDER BY 1 style statements in OceanBase Oracle mode
    • Disabling the "SQL types allowed to be executed in the SQL window" rule does not take effect
  • Database object management
    • In OceanBase MySQL mode, the names of table partitions and other objects displayed on the left object tree are surrounded by backticks
  • Result set export
    • There is no log printing for tasks
    • No data after exporting in excel format
  • PL object
    • During interactive function creation, the return value of the sys_refcursor type cannot be defined through the drop-down menu
    • The PL parameter value in OceanBase MySQL mode does not escape single quotes
  • DLM
    • The database connection pool is too small, causing task execution failure
  • Partition plan
    • Task creation failed in MySQL mode of OceanBase version 1.4.79
    • Tables that do not set a partition strategy will still perform partition plan changes
  • SQL-Check
    • The alter table xxx drop index statement cannot be recognized as a DROP INDEX statement
  • External approval integration
    • Unrecognized expression for data in indexed collection
    • The data in xml form returned by the external system will lose the root tag of the original xml during deserialization
  • Data desensitization
    • When duplicate columns are scanned, adding sensitive columns will fail
  • Project
    • After the user is granted "Personal Space" permission, he must log in again for it to take effect
    • Transaction timeout occurred when synchronizing a large number of databases or schemas to the project
    • Unable to filter work orders by project dimension
    • Project OWNER can remove all users with DBA roles in the project
  • Bastion integration
    • Inactive connections are not cleaned up
  • Recycle bin
    • Unable to delete specific objects in Recycle Bin
  • Mock data
    • Task takes up too much memory
    • Does not support ZHSGB232 encoding
    • OceanBase MySQL and native MySQL mode cannot generate tasks for bit types with a width below 8
    • Unable to skip auto-incremented primary key columns
    • The bit type width displays incorrectly in OceanBase MySQL and native MySQL modes
  • Database change task
    • Memory overflow error occurs when uploading large files
  • Full link trace
    • The memory overflow problem caused by adding the driver to the full-link diagnosis
  • Shadow table sync
    • After the work order is approved or rejected, the approver cannot view the task details
  • obclient integration
    • Repeated creation of operating system users with the same name results in error reports
  • Tickets
    • Creating a work order takes too long
    • There is a "Pending Approval" work order for another project in the "Pending Approval" work order list
  • Operation record
    • The "Data Source" column in the operation record is empty
    • SQL execution events are not logged
    • Open SQL window event is not logged
Assets 8
Loading