Skip to content

Releases: stoneatom/stonedb

stonedb-5.7-v1.0.4-alpha

30 Jun 11:08
@Nliver Nliver
5.7-v1.0.4-alpha
This tag was signed with the committer’s verified signature.
Nliver Nliver
SSH Key Fingerprint: 3/eMNLgNjLdGPHvCEwqTp6ymBgUegs3YaCBLPxPYujA Learn about vigilant mode.
bf353dc
This commit was created on github.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
stonedb-5.7-v1.0.4-alpha Latest
Latest

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 #1805
  2. Fixed a crash caused by the result set of the union all clause, #1875
  3. Fixed a crash caused by using aggregate functions in large data scenarios, #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. #1187
  2. Fix the incorrect result set problem when using case…when in derived table. #1784
  3. Fix the incorrect result problem caused by precision loss when performing bit operations when the type is time. #1173
  4. Fix the incorrect query result problem caused by overflow when the type is bigint. #1564
  5. Fix the incorrect result problem when the filter condition is hexadecimal. #1625
  6. Fix the problem that the default value on the table did not take effect when importing data using the “load data” command. #1865
  7. Modify the default field separator of the load command to make it consistent with mysql behavior. #1609
  8. Fix the query error caused by abnormal metadata. #1822
  9. Improve MTR stability on github.

What's Changed

Read more

Contributors

adofsauron, RingsC, and 12 other contributors
Assets 5
Loading
0 Join discussion

stonedb-8.0-v1.0.1-beta

01 Jun 12:43
@Nliver Nliver
8.0-v1.0.1-beta
This tag was signed with the committer’s verified signature. The key has expired.
Nliver Nliver
GPG key ID: 72B8C8870531C993
Expired
Learn about vigilant mode.
06d25fc
Compare
Choose a tag to compare
stonedb-8.0-v1.0.1-beta

8.0-v1.0.1-beta

  • Version Number: 8.0-v1.0.1-beta
  • Release Date: 2023-06-01

What's Changed

Full Changelog: 8.0-v1.0.1-alpha...8.0-v1.0.1-beta

Contributors

hustjieke, Double0101, and 2 other contributors
Assets 4
Loading
4 Join discussion

stonedb-8.0-v1.0.1-alpha

17 May 13:03
@Nliver Nliver
8.0-v1.0.1-alpha
This tag was signed with the committer’s verified signature. The key has expired.
Nliver Nliver
GPG key ID: 72B8C8870531C993
Expired
Learn about vigilant mode.
fbae81f
Compare
Choose a tag to compare
stonedb-8.0-v1.0.1-alpha

8.0-v1.0.1-alpha

  • Version Number: 8.0-v1.0.1-alpha
  • Release Date: 2023-05-17

What's Changed

  • feat(stonedb): init mysql 8.0 to branch stonedb-dev #512 by @hustjieke in #517
  • fix(stonedb): add missing files provoke by .gitignore #532 by @hustjieke in #533
  • feat(stonedb8.0:load binlog): support mysql load binlog. (#530) by @lujiashun in #531
  • fix(stonedb8.0): fix Tianmu engine for union primary key crash (#534) by @DandreChen in #556
  • feat(stonedb8.0): mysql load sql with set clause should report warning. (#551) by @lujiashun in #552
  • feat(StoneDB 8.0): parent_lex->result is nullptr in "select ... from" clause without "into outfile/dumpfile". (#557) by @lujiashun in #572
  • feat(StoneDB 8.0): thd->no_errors no_errors is deleted. (#574) by @lujiashun in #575
  • feat(StoneDB 8.0): refactor ConditionNumberFromMultipleEquality function. (#583) by @lujiashun in #585
  • feat(StoneDB 8.0): change mysql8.0 boost directory & add cmake of marisa and rocksdb by @DandreChen in #588
  • feat(StoneDB 8.0): Fix up the compiling extra-semi warnings. (#547) by @lujiashun in #592
  • feat(StoneDB 8.0): Query_block->braces is deleted by MySQL 8.0 (#593) by @DandreChen in #594
  • feat(StoneDB 8.0): Fix codes aboout JoinType. (#543) by @lujiashun in #562
  • feat(StoneDB 8.0): Field::ptr is a protected member. (#603) by @lujiashun in #604
  • feat(StoneDB 8.0): st_select_lex::set_join is deleted in mysql8.0. (#598) by @lujiashun in #602
  • feat(StoneDB 8.0): fix stonedb 8.0 compile failed (#606) by @DandreChen in #607
  • feat(CI/CD):chenge CI/CD use compile-mtr.yml(#610) by @zsp108 in #611
  • fix(StoneDB 8.0):change mergify configure check-success(#612) by @zsp108 in #616
  • feat(StoneDB 8.0): format tianmu engine's code according to clang-format file. (#618) by @lujiashun in #619
  • feat(StoneDB 8.0): lex->derived_tables & thd->fill_derived_tables() is deleted in MySQL8.0. (#548) by @DandreChen in #617
  • feat(StoneDB 8.0): 'bool partitioned' parameter is added by MySQL 8.0 in handlerton->create function. (#596) by @lujiashun in #615
  • feat(StoneDB8.0):StoneDB 8.0 add MTR(#625) by @zsp108 in #626
  • feat(StoneDB 8.0): dd::Table * parameter is added by MySQL 8.0 in handle api. (#595) by @DandreChen in #623
  • feat(tianmu): Changes the names of file to follow the convention(#576) by @RingsC in #628
  • feat(StoneDB 8.0): remove 'build' from .gitignore file. (#629) by @lujiashun in #630
  • feat(tianmu): Delete the added code to find root cause (#541) by @RingsC in #633
  • feat(StoneDB 8.0): fix up the compiling 'cast-qual' warnings. (#547) by @lujiashun in #639
  • feat(StoneDB 8.0): Replace Query_result::prepare2() with Query_result::start_execution. (#539) by @DandreChen in #638
  • feat(StoneDB 8.0): Fix up the compiling warnings(miscellaneous). (#547) by @lujiashun in #640
  • feat(tianmu): Improve tianmu readability(#11) by @RingsC in #644
  • feat(StoneDB 8.0):add complier image by centos 7(#652) by @zsp108 in #653
  • feat(tianm): Improve Tianm readability (#11) by @RingsC in #654
  • feat(StoneDB 8.0): Fix up overloaded-virtual warning in function select_tianmu_export::prepare. (#547) by @lujiashun in #645
  • feat(StoneDB 8.0): Fix up format-security/class-memaccess warnings. (#547) by @lujiashun in #655
  • fix(StoneDB 8.0): fix ERROR 2013 (HY000): Lost connection to MySQL server during query. (#650) by @lujiashun in #657
  • fix(mysql-test): add_comlumn test failed #648 by @hustjieke in #651
  • fix(StoneDB 8.0):clang-format check storage/tianmu(#667) by @zsp108 in #668
  • feat(tianmu): introduce the JOIN::optimize to tianmu (#545) by @RingsC in #666
  • feat(mtr): add more testcases in mtr #685 by @hustjieke in #686
  • feat(tianmu): Introudce the JOIN::optimize to Tianmu (#545) by @RingsC in #690
  • feat(StoneDB 8.0): adapt the Tianmu engine query interface to MySQL8.0 (#681) by @DandreChen in #683
  • fix(tianmu): add file extension of tianmu into hton to fix drop database error #662 by @hustjieke in #693
  • feature(tianmu): check whether there is least one tianmu table in Query_expression (#708) by @DandreChen in #709
  • feat(tianmu): To support ARM arch (#696). by @RingsC in #714
  • feat(StoneDB 8.0): sql command "show status" support "tianmu status variables". (#703) by @lujiashun in #704
  • fix(StoneDB 8.0):rename pull_requests.yml and change make -jnproc by @zsp108 in #677
  • feat(tianmu):fix code to repair order by command (#715) by @DandreChen in #716
  • feat(tianmu): to adapt group by command to MySQL8.0.(#718) by @DandreChen in #721
  • fix(mtr):rename *.testbak to *.test and repair some test case by @zsp108 in #725
  • feat(handler): improve code readability #719 by @hustjieke in #720
  • feat(StoneDB 8.0): add some mtr test case. (#723) by @lujiashun in #724
  • feat(tianmu): Introudce the JOIN::optimize to Tianmu(#545) by @RingsC in #728
  • feature(tianmu): to support explain the table of Tianmu engine (#726) by @DandreChen in #730
  • feat(StoneDB 8.0): tianmu_insert_delayed decides the binary log file events. (#723) by @lujiashun in #729
  • feat(handler): move ha_rcengine.cpp into ha_tianmu.cpp #691 by @hustjieke in #738
  • feat(cmake): update tianmu cmake file(#749) by @RingsC in #750
  • feat(StoneDB 8.0): adapt mtr 'issue364.test'. (#723) by @lujiashun in #742
  • feat(tianmu): Improve Tianmu code (#11) by @RingsC in #757
  • feat(StoneDB 8.0): support view query,adapt mtr "issue342" testcase. (#743) by @lujiashun in #753
  • feat(.*): improve code readability #11 by @hustjieke in #758
  • feat(StoneDB 8.0): adapt mtr test cases:issue502-2/issues_tx417/issue496/issue745. (#770) by @lujiashun in #772
  • feat(tianmu): adapt update mtr testcase for MySQL 8.0 (#779) by @DandreChen in #780
  • fix(tianmu): feature: The error display is too general, and the cause of the error cannot be clearly located #706 by @CodingSuen in #787
  • fix(tianmu): fix throw exception while execute a union sql. (#671) by @lujiashun in #807
  • fix(tianmu): bug for truncate table failed #759 by @hustjieke in #805
  • feat(StoneDB 8.0): adapt "mysqld --version" feature. (#813) by @lujiashun in #816
  • feat(StoneDB 8.0): adapt testcase insert_select.test/flow_control_function.test. (#777) by @lujiashun in #799
  • feat(mtr): add create table test in mtr #695 by @hustjieke in #825
  • feat(StoneDB 8.0): fix memory leak using valgrind(definitely lost memory). (#817) by @lujiashun in #833
  • feat(StoneDB 8.0): Improve the readbility of stonedb. (#11) by @lujiashun in #832
  • feat(tianmu):Improve the readbility of stonedb.(#11) by @DandreChen in #841
  • fix(tianmu): group_concat.test has in-consistent behavior in CICD and prompt mode (#834) by @RingsC in #843
  • feat(tianmu): Improve the tianmu code (#11) by @RingsC in #858
  • feat(tianmu): fix up the compile warnings on CentOS. (#844) by @lujiashun in #859
  • feat(tianmu): change all class members forms like a_member_ #11 by @hustjieke in #855
  • fix(StoneDB 8.0): fix duplicate 'lc-messages-dir' config item...
Read more

Contributors

RingsC, hustjieke, and 10 other contributors
Assets 2
Loading

stonedb-5.7-v1.0.3-GA

20 Mar 08:31
@Nliver Nliver
5.7-v1.0.3-GA
b6380d1
Compare
Choose a tag to compare
stonedb-5.7-v1.0.3-GA

V1.0.3-GA

  • Version Number: 1.0.3
  • Release Date: 2023-03-20

Compared to 1.0.2, StoneDB 1.0.3 has done many feature improvements and bug fixes, mainly including：

Primary/Secondary Deployment

  • Reconstructed the binlog mechanism to filter out DDL statements that are not supported by the Tianmu storage engine.
  • Added an argument named NO_KEY_ERROR for SQL mode to directly skip DDL statements that are not supported by the SQL layer, instead of reporting errors.

Syntax:

## At global level:
mysql>set global sql_mode='NO_KEY_ERROR';

## At session level:
mysql>set session sql_mode='NO_KEY_ERROR';

## Configuration file my.cnf:
[mysqld] 
sql_mode='NO_KEY_ERROR'

Ecosystem Adaptation

Better adapted to the ecosystem to display the version number of StoneDB.

Perfomance

Improved the primary/secondary synchronization performance. #1213

Bug Fixes

The following bugs are fixed:

  • Incorrect result is returned when an ALTER TABLE statement is executed to add a TIMESTAMP field. #1327
  • Incorrect result is returned for an UPDATE operation on a table after it is modified by an ALTER TABLE statement. #1253
  • Incorrect result is returned for a query on BIGINT data that is unsigned. #1203
  • An error is reported when a statement is executed to load data. #1209
  • The result returned for an AVG function call is incorrect. #1125
  • An error is reported when an ALTER TABLE statement is executed to change the data type of a field. #752
  • Other bugs. #103#1230#1255#1188#1262

Supported OSs

  • CentOS 7.6 and later
  • Ubuntu 20.0

What's Changed

Read more

Contributors

adofsauron, RingsC, and 13 other contributors
Assets 6
Loading
1 Join discussion

stonedb-5.7-v1.0.3-beta

08 Mar 14:35
@Nliver Nliver
5.7-v1.0.3-beta
683851a
Compare
Choose a tag to compare
stonedb-5.7-v1.0.3-beta Pre-release
Pre-release

V1.0.3-beta

  • Version Number: 1.0.3
  • Release Date: 2023-03-07

Compared to 1.0.2, StoneDB 1.0.3 has done many feature improvements and bug fixes, mainly including：

Primary/Secondary Deployment

  • Reconstructed the binlog mechanism to filter out DDL statements that are not supported by the Tianmu storage engine.
  • Added an argument named NO_KEY_ERROR for SQL mode to directly skip DDL statements that are not supported by the SQL layer, instead of reporting errors.

Syntax:

## At global level:
mysql>set global sql_mode='NO_KEY_ERROR';

## At session level:
mysql>set session sql_mode='NO_KEY_ERROR';

## Configuration file my.cnf:
[mysqld] 
sql_mode='NO_KEY_ERROR'

Ecosystem Adaptation

Better adapted to the ecosystem to display the version number of StoneDB.

Perfomance

Improved the primary/secondary synchronization performance. #1213

Bug Fixes

The following bugs are fixed:

  • Incorrect result is returned when an ALTER TABLE statement is executed to add a TIMESTAMP field. #1327
  • Incorrect result is returned for an UPDATE operation on a table after it is modified by an ALTER TABLE statement. #1253
  • Incorrect result is returned for a query on BIGINT data that is unsigned. #1203
  • An error is reported when a statement is executed to load data. #1209
  • The result returned for an AVG function call is incorrect. #1125
  • An error is reported when an ALTER TABLE statement is executed to change the data type of a field. #752
  • Other bugs. #103#1230#1255#1188#1262

Supported OSs

  • CentOS 7.6 and later
  • Ubuntu 20.0

What's Changed

New Contributors

Full Changelog: 5.7-v1.0.2-GA...5.7-v1.0.3-beta

Contributors

adofsauron, RingsC, and 13 other contributors
Assets 5
Loading

stonedb-5.7-v1.0.2

15 Jan 15:43
@Nliver Nliver
5.7-v1.0.2-GA
c8dee21
Compare
Choose a tag to compare
stonedb-5.7-v1.0.2

V1.0.2

Release date： January 15,2023

New features

  • Supports user-defined functions
  • Supports ESCAPE
  • Supports Primary key and Supports syntactically index constraints
  • Supports modifying the character set of table or field
  • Supports BIT data type
    • Supports Creation, change and deletion
    • Supports logical operation
  • Supports replace into statement
  • Supports syntactically unsigned and zerofill
  • Sql_mode add value 'MANDATORY_TIANMU' for mandatory Tianmu engine in table
    • The following statement demonstrates the syntax：
# Global level
mysql>set global sql_mode='STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION,MANDATORY_TIANMU';

# Session level
mysql>set session sql_mode='STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION,MANDATORY_TIANMU';

#Set my.cnf parameter file 
[mysqld] 
sql_mode        =  'STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION,MANDATORY_TIANMU'

Accessibility

  • Automatic detection and identification of installation package
  • Rapid deployment of StoneDB as an analytical database for MySQL

Stability

  • Enhanced the stability as an analytical database

Bug Fixes

The following bugs are fixed：

  • The GROUP_CONCAT() function return result set error #938
  • Bugs when use LIKE in WHERE #1162 #1157 #763
  • Bugs when use Primary key with AUTO_INCREMENT #1144 #1142
  • ALTER table..ADD numeric column, return error#1140
  • Clang-format execute failed in CI/CD#973
  • INSERT INTO table error, but some data can be inserted successfully#965
  • Query with UNION ALL return result set error #854
  • The EXTRACT() function error #845
  • Select...in...An error was reported when the date was included #829
  • Update multiple values does not work with WHERE IN clause #781
  • The syntax of the exists subquery in the TIANMU layer is compiled after the rule is incorrect, and the semantics is modified #732
  • MTR binlog.binlog_unsafe Crash #341
  • The other BUG #682 #553 #508

Behavior Change

Using the Shell script for rapid deployment of StoneDB as an analytical database for MySQL, parameter sql_mode default add value of MANDATORY_TIANMU to enable the mandatory TIANMU engine

Platforms

  • CentOS 7.6 or obove
  • Ubuntu 20

Others

  • Add more MTR test cases

What's Changed

Read more

Contributors

adofsauron, RingsC, and 15 other contributors
Assets 6
Loading

stonedb-5.7-v1.0.2

14 Jan 04:38
@hustjieke hustjieke
5.7-v1.0.2-pre-release
c8dee21
Compare
Choose a tag to compare
stonedb-5.7-v1.0.2 Pre-release
Pre-release

Changes in StoneDB_5.7_v1.0.2 (2023-01-14, Release Candidate)

Big features:

  • support User-Defined Functions(UDFs) to handle the dynamic SQL:
create function function_name();
create function function_name(args...);
create function function_name(args...) returns varchar(50)
begin
  SET @sql= select * from where id= args;
  PREPARE s1 FROM @sql;
  EXECUTE s1;
  DEALLOCATE PREPARE s1;
end $$
  • Support ESCAPE Keyword;
% :
SELECT * FROM BUG_12595 WHERE a LIKE 'hakan\%' ESCAPE '\\';
SELECT * FROM BUG_12595 WHERE a LIKE 'hakan%' ESCAPE '';
SELECT * FROM BUG_12595 WHERE a LIKE 'hakan\n%' ESCAPE '\n';
_ :
SELECT * FROM BUG_12595 WHERE a LIKE 'hakan\_' ESCAPE '\\';
SELECT * FROM BUG_12595 WHERE a LIKE 'hakan_' ESCAPE '';
SELECT * FROM BUG_12595 WHERE a LIKE 'hakan\n_' ESCAPE '\n';
  • Add syntax support for constraints primary key and index:
    Add primary key
ALTER  TABLE t2 ADD id INT AUTO_INCREMENT PRIMARYKEY;
CREATE TABLE `table_name` (`id` int NOT NULL PRIMARY KEY AUTO_INCREMENT COMMENT '主表id',`name` string NOT NULL COMMENT '名称') ;

Drop primary key

DROP INDEX PRIMARYON t;
ALTER TABLE  tbl_name  DROP {INDEX|KEY} index_name

Add index

ALTER TABLE  tbl_name  ADD {FULLTEXT|SPATIAL} [INDEX|KEY][index_name]
CREATE TABLE t1 (age INT, INDEX USING BTREE (age)) ENGINE = Tianmu;

Drop index

DROP  INDEX  index_name  ON  tbl_name;
ALTER TABLE  tbl_name  DROP {INDEX|KEY} index_name

Rename index

  ALTER TABLE  tbl_name   RENAME {INDEX|KEY} old_index_nameTOnew_index_name
  • Support changing the character set of tables/fields by using the alter table syntax；

Change character set of table:

ALTER TABLE tablename convert to character set utf8;

Change character set of table field:

ALTER TABLE tablename MODIFY latin1_text_col TEXT CHARACTERSET utf8;
ALTER TABLE tablename MODIFY latin1_varchar_col VARCHAR(M)  CHARACTERSET utf8;
ALTER TABLE tablename MODIFY latin1_text_col CHAR CHARACTERSET utf8;
ALTER TABLE tablename CHANGE colname colname TEXT CHARACT
ER SET utf8;
ALTER TABLE tablename CHANGE colname colname VARCHAR(M) CACTER SET utf8;
ALTER TABLE tablename CHANGE colname colname CHAR CHARACTER SET utf8;
  • Support BIT Data Type:
CREATE TABLE tablename(colname BIT(8));
ALTER TABLE tablename add colname BIT(8) comment '';
ALTER TABLE tablename modify column colname BIT(4);
ALTER TABLE tablename modify column colname varchar(20) ;
  • Support replace into SQL Syntax；
REPLACE INTO tablename VALUES(1,'new','2013-07-22 10:30:00');
REPLACE INTO tablename VALUES(1,'Old','2014-08-20 18:47:00');
  • Syntactically support unsigned and zerofill:
CREATE  TABLE tablename (colname int(4) unsigned zerofill);
ALTER TABLE tablename change column colname colname int(4) unsigned zerofill;
ALTER TABLE tablename change column colname colname int(4);
  • The sql_mode adds the mandatory attribute to make the tianmu as the default:
    Notes: sql_mode ='MANDATORY_TIANMU' > default_storage_engine
    Global
set global sql_mode='MANDATORY_TIANMU';

session

set sql_mode='MANDATORY_TIANMU';

my.cnf

[mysqld] 
sql_mode ='MANDATORY_TIANMU'

startup script

./mysqld --sql-mode='MANDATORY_TIANMU'
  • Complete mtr test.

Accessibility Notes

  • Automatic detection of installation package and and identification ability.
  • Rapid deployment as a secondary database for MySQL.

Docs:
The manual has been updated as the code was modified. ( #doc)

Assets 5
Loading
0 Join discussion

stonedb-5.7-v1.0.1

24 Oct 13:00
@zsp108 zsp108
5.7-v1.0.1-GA
b8cc4cf
Compare
Choose a tag to compare
stonedb-5.7-v1.0.1

Changes in StoneDB_5.7_v1.0.1 (2022-10-24, General Availability)
● Functionality Added or Changed
● Compilation Notes
● Document Notes
● Bugs Fixed
Functionality Added or Changed
● Tianmu: From StoneDB_5.7 v1.0.1, you can use delete statement to clear some data you don't need.

delete from table1;
delete from table1, table2, ...;
delete from table1 where ...;
delete from table1, table2, ... where ...;

● Tianmu: From StoneDB_5.7 v1.0.1, you can use alter table statement to modify the table structure as you need.

alter table tablename

● Tianmu: Binlog replication supported ROW format；

binlog_format = ROW

● Tianmu: Added temporary table function；

CREATE TEMPORARY TABLE IF NOT EXISTS tablename

● Tianmu: From StoneDB_5.7 v1.0.1, you can create a trigger. The trigger is a named database object that is associated with a table, and that activates when a particular event occurs for the table.

create trigger triggername

● Tianmu: Added Create table AS... union... statement；
● Tianmu: The Tianmu engine improved the performance of subqueries；
● Tianmu: Added gtest module；
● Tianmu: Added some mtr test cases；
Compilation Notes
● Added cmake parameter configuration for build

cmake  .. -DWITH_MARISA  -DWITH_ROCKSDB

Document Notes
● The manual has been updated as the code was modified. ( # address)
Bugs Fixed
● fix some inherited mtr from MySQL
● fix Tianmu bug: #282,#274,#270,#663,#669,#670,#675,#678,#682,#487,#426,#250,#247,#569,#566,#290,#736,#567,#500,#300,#289,#566,#279,#570,#571,#580,#581,#586,#589,#674,#646,#280,#301,#733 et. al.

What's Changed

Read more

Contributors

adofsauron, RingsC, and 17 other contributors
Assets 5
Loading

5.7-v1.0.1-beta

17 Sep 08:29
@hustjieke hustjieke
5.7-v1.0.1-beta
208f79d
This commit was created on github.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
5.7-v1.0.1-beta Pre-release
Pre-release 
feat(tianmu) Refactor the aggregation and The IN operator to multithr…
Assets 3
Loading

stonedb-5.7-v1.0.0

31 Aug 12:36
@hustjieke hustjieke
5.7-v1.0.0-GA
eed32f6
This commit was created on github.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
stonedb-5.7-v1.0.0

Changes in StoneDB_5.7_v1.0.0 (2022-08-31, General Availability)

  • Support for MySQL 5.7
  • Functionality Added or Changed
  • Compilation Notes
  • Configuration Notes
  • Document Notes
  • Bugs Fixed

Support for MySQL 5.7

  • Important Change: The Tianmu engine supports MySQL 5.7，base line edition MySQL 5.7.36. This change applies to the StoneDB database which would be fully compatible with the MySQL 5.7 protocols.

Functionality Added or Changed

  • Important Change: The engine name has been changed to tianmu. StoneDB is used as a HTAP database name, it is not suitable for used both as an engine name. As the dissusion result, we choose tianmu as our new eninge name:
mysql> show engines;
+----------------+---------+--------------------------+--------------+------+------------+
| Engine         | Support | Comment                  | Transactions | XA   | Savepoints |
+----------------+---------+--------------------------+--------------+------+------------+
| TIANMU         | DEFAULT | Tianmu storage engine    | YES          | NO   | NO         |
+----------------+---------+--------------------------+--------------+------+------------+

  • Tianmu: Improved the aggregation capabilities of the decimal data type.

  • Tianmu: Improved the readability of code. The code does not spererate logically, or the variables name can not be understooed by the literal meaning. To refactor code make it more readable to anyone who are the first to read that. For example: Changes int DoGetSomething(); to int GetSomethingXXX();, int GetNoNulls() to int GetNumOfNulls().

  • Tianmu: The date-related functions (such as DATE_ADD, DATE_SUB) can be queried (DATE_ADD|DATE_SUB) when creating view using the date func.(BUG #342)

Compilation Notes

  • The version of the Boost library for server builds is now 1.66.0.

  • The version of the Rocksdb for server builds is now 6.12.6.

Configuration Notes

  • Important Change: Changed default config file stonedb.cnf to my.cnf. (feature #182)

  • Important Change: Use tianmu as the default storage engine. (feature #255)

Document Notes

  • The manual has been updated as the code was modified. ( # address)

Bugs Fixed

Assets 3
Loading
1 Join discussion