mirror of
https://github.com/actiontech/dble.git
synced 2026-05-11 17:11:36 -05:00
fix typo
This commit is contained in:
@@ -9,24 +9,24 @@ DBLE is a high scalability middle-ware for MySQL sharding.
|
||||
As your business grows, you can use DBLE to replace the origin single MySQL instance.
|
||||
|
||||
- __Compatible with MySQL protocol__
|
||||
Use DBLE as MySQL. You can replace MySQL with DBLE to power your application without changing a single line of code in most cases.
|
||||
Use DBLE as MySQL. You can replace MySQL with DBLE to power your application without changing a single line of code in most cases.
|
||||
|
||||
- __High availability__
|
||||
DBLE server can used as clustered,business will not suffer with single node fail.
|
||||
DBLE server can used as clustered, business will not suffer with single node fail.
|
||||
|
||||
- __SQL Support__
|
||||
Support(some in Roadmap) SQL 92 standard and MySQL dialect. We support complex SQL query like group by, order by, distinct ,join ,union, subquery(in Roadmap) and so on.
|
||||
Support(some in Roadmap) SQL 92 standard and MySQL dialect. We support complex SQL query like group by, order by, distinct, join ,union, sub-query(in Roadmap) and so on.
|
||||
|
||||
- __Complex Query Optimize__
|
||||
Optimize the complex query, including, without limitation, Global-table join sharding-table,ER-relation tables,Subquerys,Simplifying select items,and the like.
|
||||
- __Complex Query Optimization__
|
||||
Optimize the complex query, including, without limitation, Global-table join sharding-table, ER-relation tables, Sub-Queries, Simplifying select items, and the like.
|
||||
|
||||
- __Distributed Transaction__
|
||||
Support Distributed Transaction using two-phase commit. You can choose normal mode for performance or XA mode for data safe,of cource,the XA mode dependent on MySQL5.7's XA Transaction, MySQL node's high availability and data reliability of disk.
|
||||
Support Distributed Transaction using two-phase commit. You can choose normal mode for performance or XA mode for data safe, of course, the XA mode dependent on MySQL5.7's XA Transaction, MySQL node's high availability and data reliability of disk.
|
||||
|
||||
|
||||
## History
|
||||
Firstly,hanks for [MyCat](https://github.com/MyCATApache/Mycat-Server)'s contribution in the open source community.
|
||||
But for us, focusing more attention on support for MySQL is a better choise.So we removed the support for other heterogeneous database,deeply improved/optimized the compatible, complex query and distributed transaction. And of cource, fixed some bugs during testing.
|
||||
But for us, focusing more attention on support for MySQL is a better choice.So we removed the support for other heterogeneous database,deeply improved/optimized the compatible, complex query and distributed transaction. And of course, fixed some bugs during testing.
|
||||
|
||||
For more details, see[Roadmap](./docs/ROADMAP.md) or [Issues](https://github.com/actiontech/dble/issues) .
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Contribution Guide
|
||||
Dble is a community driven open source project and we welcome any contributor.This guide documents the best way to make various types of contribution to Dble, including what is required before submitting a code change.
|
||||
Of couse, contributing doesn’t just mean writing code. Improving documentation and reporting bugs are also welcome.
|
||||
Of course, contributing doesn't just mean writing code. Improving documentation and reporting bugs are also welcome.
|
||||
|
||||
## Contributing Bug Reports
|
||||
Ideally, bug reports are accompanied by a proposed code change to fix the bug. This isn’t always possible, as those who discover a bug may not have the experience to fix it. A bug may be reported but without creating a pull request (see below).
|
||||
@@ -20,7 +20,7 @@ This part outlines some conventions about development workflow, commit message f
|
||||
|
||||
Before you move on, please make sure what your issue and/or pull request is, a bug fix or an architecture change.
|
||||
|
||||
You konw that review can take hours or days of committer time, so
|
||||
You know that review can take hours or days of committer time, so
|
||||
everyone benefits if contributors focus on changes that are useful, clear, easy to evaluate, and already pass basic checks.
|
||||
|
||||
Besides all above, each issue should be filed with template.
|
||||
@@ -29,7 +29,7 @@ Besides all above, each issue should be filed with template.
|
||||
### Is this a bug fix?
|
||||
|
||||
Bug fixes usually come with tests. With the help of continuous integration test, patches can be easy to review. Please update the unit tests so that they catch the bug!
|
||||
Issue example will comming soon.
|
||||
IMPORTANT:Issue example will be comming soon.
|
||||
|
||||
### Is this an architecture improvement?
|
||||
|
||||
@@ -37,11 +37,12 @@ Some examples of "Architecture" improvements:
|
||||
|
||||
- Improving test coverage.
|
||||
- Decoupling logic or creation of new utilities.
|
||||
- Making code more resilient (sleeps, backoffs, reducing flakiness, etc).
|
||||
- Making code more resilient (sleeps, back offs, reducing flakiness, etc).
|
||||
- Improving performance.
|
||||
|
||||
|
||||
If you are improving the quality of code, then justify/state exactly what you are 'cleaning up' in your Pull Request so as to save reviewers' time. An example will be comming soon.
|
||||
If you are improving the quality of code, then justify/state exactly what you are 'cleaning up' in your Pull Request so as to save reviewers' time.
|
||||
IMPORTANT: An example will be comming soon.
|
||||
|
||||
If you're making code more resilient, test it locally to demonstrate how exactly your patch changes things.
|
||||
|
||||
@@ -130,7 +131,7 @@ in a few cycles.
|
||||
|
||||
### Step 6: Push
|
||||
|
||||
When ready to review (or just to establish an offsite backup or your work),
|
||||
When ready to review (or just to establish an off-site backup or your work),
|
||||
push your branch to your fork on `github.com`:
|
||||
|
||||
```sh
|
||||
|
||||
+4
-4
@@ -2,9 +2,9 @@
|
||||
## 1.Download DBLE Release
|
||||
Get package from https://github.com/actiontech/DBLE/releases
|
||||
|
||||
## 2.Pepare
|
||||
## 2.Prepare
|
||||
### 2.1 MySQL
|
||||
Make sure there is at least one MySQL Instance with url $url(e.g, localhost:3306) ,$user(e.g., test) and $password(e.g., testPsw) in your machine.
|
||||
Make sure there is at least one MySQL Instance with url $url(e.g., localhost:3306) ,$user(e.g., test) and $password(e.g., testPsw) in your machine.
|
||||
Add 4 database ,the SQL as below:
|
||||
|
||||
```
|
||||
@@ -33,7 +33,7 @@ cp server_template.xml server.xml
|
||||
|
||||
## 4.Config
|
||||
Edit the file schema.xml.
|
||||
Find the dataHost element ,delete all the writeHost/readHost element below.
|
||||
Find the dataHost element, delete all the writeHost/readHost element below.
|
||||
Create a new writeHost element like
|
||||
```
|
||||
<writeHost host="hostM1" url="$url" user="$user" password="$password"/>
|
||||
@@ -63,7 +63,7 @@ You should see "Server startup successfully. see logs in logs/dble.log".
|
||||
|
||||
## 5.connect
|
||||
As a distributed-database imitate mysql,you can use all Mysql classic connection.
|
||||
In this case you can connect to the DBLE where commond:
|
||||
In this case you can connect to the DBLE using command:
|
||||
```
|
||||
mysql -p -P8066 -h 127.0.0.1 -u root
|
||||
```
|
||||
|
||||
+3
-3
@@ -9,8 +9,8 @@ This document defines the roadmap for DBLE development.
|
||||
- [x] REPLACE Syntax
|
||||
- [x] Join (LEFT JOIN / RIGHT JOIN / CROSS JOIN)
|
||||
- [x] Union
|
||||
- [x] Simple Subquery
|
||||
- [ ] Correlated Subquery
|
||||
- [x] Simple Sub-query
|
||||
- [ ] Correlated Sub-Query
|
||||
- [x] Functions support
|
||||
- [x] Type Conversion in Expression Evaluation
|
||||
- [x] Operators
|
||||
@@ -41,7 +41,7 @@ This document defines the roadmap for DBLE development.
|
||||
- [ ] Smooth Offline
|
||||
|
||||
##### __Optimization__
|
||||
- [x] Global tablle
|
||||
- [x] Global table
|
||||
- [x] ER table
|
||||
- [x] Push down Where Filter
|
||||
- [x] Simplify Where Filter
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 56 KiB After Width: | Height: | Size: 72 KiB |
Reference in New Issue
Block a user