Skip to content

Navigation Menu

Sign in
Sign up

stonedb-5.7-v1.0.4-alpha #1920

Nliver announced in Announcements
Discussion options

Release Notes for stonedb-5.7-v1.0.4-alpha

  • Version Number: 5.7-v1.0.4-alpha
  • Release Date: 2023年06月30日

Stability:

  1. Fixed a crash caused by incremental data when importing data bug: Incremental data causing instance crash. #1805
  2. Fixed a crash caused by the result set of the union all clause, bug: The instance is crashed when extracting data from the union all result set of decimal and integer. #1875
  3. Fixed a crash caused by using aggregate functions in large data scenarios, bug: The instance is crashed if the aggregate function out of bounds #1855

New features

2.1. Support for update ignore syntax feature.

When updating tianmu, records with primary key conflicts will be skipped and subsequent update operations will be performed.
For example:

CREATE TABLE t1 (id int(11) NOT NULL auto_increment, parent_id int(11) DEFAULT '0' NOT NULL, level tinyint(4)
DEFAULT '0' NOT NULL, PRIMARY KEY (id)) engine=tianmu;
INSERT INTO t1 VALUES (3,1,1),(4,1,1);

Executing the update ignore t1 set id=id+1; statement will ignore the update of PK=3, because the updated primary key will conflict with PK=4. Then continue to execute the update of pk=4, and the updated PK=5.

mysql> CREATE TABLE t1 (id int(11) NOT NULL auto_increment, parent_id int(11) DEFAULT '0' NOT NULL, level tinyint(4)
 -> DEFAULT '0' NOT NULL, PRIMARY KEY (id)) engine=tianmu;
Query OK, 0 rows affected (0.01 sec)
mysql> INSERT INTO t1 VALUES (3,1,1),(4,1,1);
Query OK, 2 rows affected (0.01 sec)
Records: 2 Duplicates: 0 Warnings: 0
mysql> update t1 set id=id+1;
ERROR 1062 (23000): Duplicate entry '4' for key 'PRIMARY'
mysql> select * from t1; 
+----+-----------+-------+
| id | parent_id | level |
+----+-----------+-------+
| 3 | 1 | 1 |
| 4 | 1 | 1 |
+----+-----------+-------+
2 rows in set (0.00 sec)
mysql> update ignore t1 set id=id+1;
Query OK, 2 rows affected (0.00 sec)
Rows matched: 2 Changed: 2 Warnings: 0
mysql> select * from t1; 
+----+-----------+-------+
| id | parent_id | level |
+----+-----------+-------+
| 3 | 1 | 1 |
| 5 | 1 | 1 |
+----+-----------+-------+
2 rows in set (0.00 sec)

2.2 Support row format for "load data" statement.

When stonedb is used as the primary database, the load statement will be executed on the backup database in the form of "insert into".

2.3 Support AggregatorGroupConcat function

mysql> select GROUP_CONCAT(t.id) from sequence t;
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| GROUP_CONCAT(t.id) |
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 3000000000010000,3000000000010001,3000000000010002,3000000000010003,3000000000010004,3000000000010005,3000000000010006,3000000000010007,3000000000010008,3000000000010009,3000000000010010 |
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.01 sec)

2.4 Support using select 111 or select 111 from dual scenarios in uion/union all

mysql> select id from tt union all select 2222 c1 from dual;
+------+
| id |
+------+
| 1111 |
| 2222 |
+------+
mysql> select id from tt union all select 2222 ;
+------+
| id |
+------+
| 1111 |
| 2222 |
+------+
-- PS:select 111(from dual) appears in a position other than that of the first clause

Others Bug fixs

  1. Fix the default value problem of adding columns in the master and slave scenarios. bug: (Primary/Secondary)After an integer column is added,InnoDB defaults to 0, but tianmu defaults to null. #1187
  2. Fix the incorrect result set problem when using case...when in derived table. bug: result of querying a value from an empty derived table have select case is not consistent with innodb #1784
  3. Fix the incorrect result problem caused by precision loss when performing bit operations when the type is time. bug: Bit Operators and Functions problems #1173
  4. Fix the incorrect query result problem caused by overflow when the type is bigint. bug: bigint type, return wrong result; #1564
  5. Fix the incorrect result problem when the filter condition is hexadecimal. bug: When using where to filter hexadecimal formate data, return incorrect #1625
  6. Fix the problem that the default value on the table did not take effect when importing data using the "load data" command. bug: load data , the default value of the field does not take effect #1865
  7. Modify the default field separator of the load command to make it consistent with mysql behavior. bug: load data return error #1609
  8. Fix the query error caused by abnormal metadata. bug: Error 1030 occurred in the query. #1822
  9. Improve MTR stability on github.

What's Changed

New Contributors

Full Changelog: 5.7-v1.0.3-GA...5.7-v1.0.4-alpha

This discussion was created from the release stonedb-5.7-v1.0.4-alpha.
You must be logged in to vote

Replies: 0 comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant

AltStyle によって変換されたページ (->オリジナル) /