PullRequest: 753 zyj-V4.0.0-aone8
This commit is contained in:
obdev
parent
e25251a7c2
commit
83a63d2e80
490
.menu_map.yml
490
.menu_map.yml
|
|
@ -1,245 +1,245 @@
|
|||
100.oceanbase-database-overview=OceanBase 简介
|
||||
200.quick-start=快速上手
|
||||
100.Getting-started-with-OceanBase-SQL=上手 OceanBase SQL
|
||||
200.Create-a-sample-application=创建示例应用程序
|
||||
300.Experience-the-advanced-features-of-OceanBase=体验 OceanBase 高级特性
|
||||
100.Experience-Scalable-OLTP=体验 Scalable OLTP
|
||||
300.developer-guide=应用开发
|
||||
100.client-connects-to-oceanbase-database=客户端连接 OceanBase 数据库
|
||||
1400.database-connection-pool-configuration-example=数据库连接池配置示例
|
||||
600.c-application=C 应用程序
|
||||
200.create-and-manage-database-objects=创建和管理数据库对象
|
||||
400.data-type=数据类型
|
||||
600.create-and-manage-tables=创建和管理表
|
||||
700.create-and-manage-partition-table=创建和管理分区表
|
||||
800.create-and-manage-indexes=创建和管理索引
|
||||
1000.create-and-manage-views=创建和管理视图
|
||||
1100.managing-and-creating-sequences=创建和管理序列
|
||||
1200.create-and-manage-triggers=创建和管理触发器
|
||||
300.query=查询
|
||||
800.multi-table-join-queries=多表关联查询
|
||||
900.use-operators-and-functions-in-queries=在查询中使用操作符和函数
|
||||
1000.execution-plan=执行计划
|
||||
400.about-dml-statements-and-transactions=关于 DML 语句和事务
|
||||
100.dml-statement=DML 语句
|
||||
200.transaction=事务
|
||||
500.common-errors-and-solutions-mysql=MySQL 模式下常见报错
|
||||
300.timeout=超时相关
|
||||
400.user-2=用户相关
|
||||
500.table-related-functions=表相关
|
||||
600.constraint-related-functions=约束相关
|
||||
700.sql-related-commands=SQL 相关
|
||||
400.installation-and-deployment=部署数据库
|
||||
200.local-deployment=本地部署
|
||||
400.highly-available-deployment=高可用部署
|
||||
500.administrator-guide=管理数据库
|
||||
500.database-connection-and-routing=数据库连接和路由
|
||||
200.obproxy-management=管理 OBProxy
|
||||
200.manage-obproxy-clusters=管理 OBProxy 集群
|
||||
300.obproxy-management=管理 OBProxy
|
||||
300.database-connection=连接数据库
|
||||
500.logical-connection=逻辑连接
|
||||
600.driver-management=驱动管理
|
||||
700.route-management=路由管理
|
||||
400.odp-routing-policy=ODP 路由策略
|
||||
600.basic-database-management=集群和多租户管理
|
||||
100.manage-clusters=管理集群
|
||||
300.manage-cluster-parameters=管理集群参数
|
||||
400.manage-zones-in-a-cluster=管理集群中的 Zone
|
||||
500.manage-observers=管理 OBServer
|
||||
200.configuration-management=配置管理
|
||||
300.manage-resources=管理资源
|
||||
300.manage-resource-units=管理资源单元
|
||||
500.manage-resource-pools-1=管理资源池
|
||||
400.manage-tenants-1=管理租户
|
||||
400.manage-tenants-2=管理租户
|
||||
500.manage-users-and-permissions=管理用户和权限
|
||||
100.users-and-permissions=用户及权限介绍
|
||||
300.mysql-3=MySQL 模式
|
||||
1300.manage-tenant-parameters=管理租户参数
|
||||
500.manage-data-storage=管理数据存储
|
||||
100.dump-management-1=转储管理
|
||||
200.merge-management-1=合并管理
|
||||
300.data-compression-1=数据压缩
|
||||
700.memory-management-1=管理内存
|
||||
800.management-process=管理进程
|
||||
900.manage-logs=管理日志
|
||||
200.log-print-level=日志打印级别
|
||||
300.manage-the-size-and-quantity-of-log-files-2=日志文件大小及数量管理
|
||||
400.view-logs-2=查看日志
|
||||
700.database-object-management=数据库对象管理
|
||||
100.manage-databases=管理数据库
|
||||
200.manage-tables=管理表
|
||||
400.manage-indexes=管理索引
|
||||
800.distributed-storage-management=分布式存储管理
|
||||
200.manage-partition-table=管理分区
|
||||
900.create-partition-table-index-3=创建分区表索引
|
||||
400.manage-replicas=管理副本
|
||||
500.locality-management-1=管理 Locality
|
||||
900.performance-tuning-guide=性能调优
|
||||
200.performance-related-tools=性能相关工具
|
||||
100.system-tools=系统工具
|
||||
200.internal-table=内部表
|
||||
300.log-information=日志
|
||||
300.system-tuning=系统调优
|
||||
200.database-parameter-tuning=数据库参数调优
|
||||
300.obproxy-parameter-optimization=OBProxy 参数调优
|
||||
400.business-model-tuning=业务模型调优
|
||||
500.sql-optimization=SQL 调优指南
|
||||
200.sql-execution-plan=SQL 执行计划
|
||||
200.execution-plan-operator=执行计划算子
|
||||
300.distributed-execution-plan=分布式执行计划
|
||||
400.sql-optimization-1=SQL 调优
|
||||
300.monitor-sql-execution-performance=SQL 执行性能监控
|
||||
400.sql-performance-analysis-example=SQL 性能分析示例
|
||||
400.optimizer-statistics=优化器统计信息
|
||||
200.statistics-collection-methods=统计信息收集方式
|
||||
300.statistics-management=统计信息管理
|
||||
500.query-rewrite=查询改写
|
||||
600.query-optimization=查询优化
|
||||
100.access-path=访问路径
|
||||
200.join-algorithm=联接算法
|
||||
700.manage-execution-plans=管理执行计划
|
||||
600.performance-whitepaper=性能测试
|
||||
1000.high-data-availability=高可用和容灾
|
||||
100.administrator-guide-flashback=闪回
|
||||
200.backup-and-restoration-management=备份恢复管理
|
||||
300.log-archive=日志归档
|
||||
400.data-backup=数据备份
|
||||
500.cleaning-up-backed-up-data=清理备份
|
||||
600.restore-data=恢复数据
|
||||
1100.operation-and-maintenance-management=运维管理
|
||||
200.scale-out-and-scale-in-1=扩容和缩容
|
||||
200.cluster-level-scale-out-and-scale-in=集群级别的扩容和缩容
|
||||
100.scale-out=扩容
|
||||
200.shrink-1=缩容
|
||||
300.scale-in-and-scale-out-of-tenant-resources=租户内资源的扩容和缩容
|
||||
400.monitoring-and-alerting=监控和告警
|
||||
200.monitoring-1=监控
|
||||
300.alert-1=告警
|
||||
500.daily-inspection=日常巡检
|
||||
200.full-link-detection=全链路诊断
|
||||
600.performance-diagnosis=性能诊断
|
||||
800.emergency-response=应急处理
|
||||
300.common-emergency-response=常见应急问题处理
|
||||
100.issues-in-the-hardware-environment=硬件环境导致的问题
|
||||
200.problems-caused-by-capacity-changes=容量变化导致的问题
|
||||
300.other-problems-within-the-cluster=集群内部其他问题
|
||||
1200.data-security-management=数据库安全
|
||||
600.data-migration=数据迁移
|
||||
200.migrate-data-from-MySQL-database-to-OceanBase-database=从 MySQL 迁移到 OceanBase 数据库
|
||||
400.migrate-data-from-CSV-file-to-OceanBase-database=从 CSV 文件迁移数据到 OceanBase 数据库
|
||||
700.migrate-data-from-OceanBase-database-to-MySQL=从 OceanBase 迁移到 MySQL 数据库
|
||||
700.reference=参考指南
|
||||
100.oceanbase-database-concepts=系统架构
|
||||
300.multi-tenant-architecture-1=多租户架构
|
||||
500.tenants-and-resource-management-1=租户与资源管理
|
||||
400.database-objects-1=数据库对象
|
||||
100.introduction-to-database-objects-1=数据库对象介绍
|
||||
200.table-1=表
|
||||
200.data-type-3=数据类型
|
||||
300.index-1=索引
|
||||
400.partition-2=分区
|
||||
500.view-2=视图
|
||||
600.system-view-2=系统视图
|
||||
700.data-integrity-1=数据完整性
|
||||
200.integrity-constraint-type-1=完整性约束类型
|
||||
500.distributed-database-objects=分布式数据库对象
|
||||
300.data-partitions-and-replicas=数据分区和分区副本
|
||||
300.partition-replica-type=分区副本类型
|
||||
400.dynamic-scaling=动态扩容和缩容
|
||||
200.scale-in-and-scale-out-of-tenant-resources-1=租户内资源的扩容和缩容
|
||||
600.data-link-1=数据链路
|
||||
200.database-proxy-1=数据库代理
|
||||
700.user-interface-and-query-language=用户接口和查询语言
|
||||
100.SQL=SQL
|
||||
100.sql-introduction=SQL 介绍
|
||||
200.sql-statement-2=SQL 语句
|
||||
500.distributed-execution-plan-2=分布式执行计划
|
||||
200.PL=PL
|
||||
800.transaction-management-1=事务管理
|
||||
100.transaction-2=事务
|
||||
500.transaction-control=事务控制
|
||||
800.distributed-transactions-1=分布式事务
|
||||
200.transaction-concurrency-and-consistency=事务并发和一致性
|
||||
300.concurrency-control-1=并发控制
|
||||
400.transaction-isolation-level=事务隔离级别
|
||||
900.storage-architecture-1=存储架构
|
||||
200.data-storage=数据存储
|
||||
300.dump-and-merge-1=转储和合并
|
||||
600.data-integrity-2=数据完整性
|
||||
1000.high-data-reliability-and-availability=数据可靠性和高可用
|
||||
100.high-availability-architecture=高可用架构
|
||||
400.data-protection=数据保护
|
||||
500.backup-and-restoration=备份恢复
|
||||
1100.database-security=数据安全
|
||||
1200.observer-node-architecture=OBServer 节点架构
|
||||
300.observer-thread-model=observer 线程模型
|
||||
500.memory-management=内存管理
|
||||
200.sql-syntax=SQL 语句
|
||||
100.system-tenants=系统租户
|
||||
200.alter-system=ALTER SYSTEM
|
||||
200.common-tenant-mysql-mode=普通租户
|
||||
100.basic-elements=基本元素
|
||||
100.data-type=数据类型
|
||||
200.numeric-1=数值类型
|
||||
300.date-and-time-types-1=日期时间类型
|
||||
400.string-2=字符类型
|
||||
500.large-object-1=大对象和文本类型
|
||||
800.json-formatted-data-type=JSON 数据类型
|
||||
200.expression-2=表达式
|
||||
300.character-set-and-collation=字符集与字符序
|
||||
400.literal=字面量
|
||||
200.operator=运算符
|
||||
400.functions=函数
|
||||
200.functions-1=单行函数
|
||||
100.date-and-time-functions-1=日期时间函数
|
||||
200.string-functions=字符串函数
|
||||
300.conversion-functions-1=转换函数
|
||||
400.mathematical-functions=数学函数
|
||||
500.comparison-functions=比较函数
|
||||
600.process-control-functions=流程控制函数
|
||||
300.aggregate-function=聚合函数
|
||||
400.analysis-functions-1=分析函数
|
||||
500.encryption-functions=加密函数
|
||||
600.information-functions=信息函数
|
||||
700.json-functions=JSON 函数
|
||||
100.create-a-function-with-json-text=创建 JSON 文本的函数
|
||||
200.a-function-to-search-for-json-text=搜索 JSON 文本的函数
|
||||
300.function-to-modify-json-text=修改 JSON 文本的函数
|
||||
400.function-that-returns-the-json-text-property=返回 JSON 文本属性的函数
|
||||
500.json-functions-1=JSON 工具函数
|
||||
600.json-aggregate-functions=JSON 聚合函数
|
||||
800.other-functions=其它函数
|
||||
500.queries-and-subqueries=查询和子查询
|
||||
600.sql-statement=SQL语句
|
||||
5100.SELECT-1-2=SELECT
|
||||
700.ddl-function=DDL 功能
|
||||
300.system-views=系统视图
|
||||
200.dictionary-view-5=字典视图
|
||||
300.performance-view-5=性能视图
|
||||
400.system-variables=系统变量
|
||||
500.system-configuration-items=系统配置项
|
||||
300.cluster-level-configuration-items-1=集群级别配置项
|
||||
400.tenant-level-configuration-items-1=租户级别配置项
|
||||
600.error-codes=错误码
|
||||
800.supporting-tools=生态工具
|
||||
100.ob-admin=ob_admin
|
||||
300.clog=clog
|
||||
200.ob-agent=OBAgent
|
||||
100.about-obagent=关于 OBAgent
|
||||
200.configuration-reference=配置引用
|
||||
300.install-and-deploy-obagent=安装部署
|
||||
400.obagent-metrics=OBAgent 指标
|
||||
400.cdc=CDC
|
||||
200.obcdc=obcdc
|
||||
100.deploy-and-use-obcdc=obcdc 部署和使用
|
||||
200.obcdc-parameters=obcdc 参数说明
|
||||
300.oblogproxy=oblogproxy
|
||||
100.install-and-deploy-oblogproxy=oblogproxy 安装部署
|
||||
400.oblogmsg=oblogmsg
|
||||
1000.mysqltest=mysqltest
|
||||
200.use-of-case=case 使用
|
||||
900.releasenotes=版本发布记录
|
||||
9900.V4.0=V4.0
|
||||
10000.V3.1=V3.1
|
||||
1.oceanbase-database-overview=OceanBase 简介
|
||||
2.quick-start=快速上手
|
||||
1.Getting-started-with-OceanBase-SQL=上手 OceanBase SQL
|
||||
2.Create-a-sample-application=创建示例应用程序
|
||||
3.Experience-the-advanced-features-of-OceanBase=体验 OceanBase 高级特性
|
||||
1.Experience-Scalable-OLTP=体验 Scalable OLTP
|
||||
3.developer-guide=应用开发
|
||||
1.client-connects-to-oceanbase-database=客户端连接 OceanBase 数据库
|
||||
14.database-connection-pool-configuration-example=数据库连接池配置示例
|
||||
6.c-application=C 应用程序
|
||||
2.create-and-manage-database-objects=创建和管理数据库对象
|
||||
4.data-type=数据类型
|
||||
6.create-and-manage-tables=创建和管理表
|
||||
7.create-and-manage-partition-table=创建和管理分区表
|
||||
8.create-and-manage-indexes=创建和管理索引
|
||||
10.create-and-manage-views=创建和管理视图
|
||||
11.managing-and-creating-sequences=创建和管理序列
|
||||
12.create-and-manage-triggers=创建和管理触发器
|
||||
3.query=查询
|
||||
8.multi-table-join-queries=多表关联查询
|
||||
9.use-operators-and-functions-in-queries=在查询中使用操作符和函数
|
||||
10.execution-plan=执行计划
|
||||
4.about-dml-statements-and-transactions=关于 DML 语句和事务
|
||||
1.dml-statement=DML 语句
|
||||
2.transaction=事务
|
||||
5.common-errors-and-solutions-mysql=MySQL 模式下常见报错
|
||||
3.timeout=超时相关
|
||||
4.user-2=用户相关
|
||||
5.table-related-functions=表相关
|
||||
6.constraint-related-functions=约束相关
|
||||
7.sql-related-commands=SQL 相关
|
||||
4.installation-and-deployment=部署数据库
|
||||
2.local-deployment=本地部署
|
||||
4.highly-available-deployment=高可用部署
|
||||
5.administrator-guide=管理数据库
|
||||
5.database-connection-and-routing=数据库连接和路由
|
||||
2.obproxy-management=管理 OBProxy
|
||||
2.manage-obproxy-clusters=管理 OBProxy 集群
|
||||
3.obproxy-management=管理 OBProxy
|
||||
3.database-connection=连接数据库
|
||||
5.logical-connection=逻辑连接
|
||||
6.driver-management=驱动管理
|
||||
7.route-management=路由管理
|
||||
4.odp-routing-policy=ODP 路由策略
|
||||
6.basic-database-management=集群和多租户管理
|
||||
1.manage-clusters=管理集群
|
||||
3.manage-cluster-parameters=管理集群参数
|
||||
4.manage-zones-in-a-cluster=管理集群中的 Zone
|
||||
5.manage-observers=管理 OBServer
|
||||
2.configuration-management=配置管理
|
||||
3.manage-resources=管理资源
|
||||
3.manage-resource-units=管理资源单元
|
||||
5.manage-resource-pools-1=管理资源池
|
||||
4.manage-tenants-1=管理租户
|
||||
4.manage-tenants-2=管理租户
|
||||
5.manage-users-and-permissions=管理用户和权限
|
||||
1.users-and-permissions=用户及权限介绍
|
||||
3.mysql-3=MySQL 模式
|
||||
13.manage-tenant-parameters=管理租户参数
|
||||
5.manage-data-storage=管理数据存储
|
||||
1.dump-management-1=转储管理
|
||||
2.merge-management-1=合并管理
|
||||
3.data-compression-1=数据压缩
|
||||
7.memory-management-1=管理内存
|
||||
8.management-process=管理进程
|
||||
9.manage-logs=管理日志
|
||||
2.log-print-level=日志打印级别
|
||||
3.manage-the-size-and-quantity-of-log-files-2=日志文件大小及数量管理
|
||||
4.view-logs-2=查看日志
|
||||
7.database-object-management=数据库对象管理
|
||||
1.manage-databases=管理数据库
|
||||
2.manage-tables=管理表
|
||||
4.manage-indexes=管理索引
|
||||
8.distributed-storage-management=分布式存储管理
|
||||
2.manage-partition-table=管理分区
|
||||
9.create-partition-table-index-3=创建分区表索引
|
||||
4.manage-replicas=管理副本
|
||||
5.locality-management-1=管理 Locality
|
||||
9.performance-tuning-guide=性能调优
|
||||
2.performance-related-tools=性能相关工具
|
||||
1.system-tools=系统工具
|
||||
2.internal-table=内部表
|
||||
3.log-information=日志
|
||||
3.system-tuning=系统调优
|
||||
2.database-parameter-tuning=数据库参数调优
|
||||
3.obproxy-parameter-optimization=OBProxy 参数调优
|
||||
4.business-model-tuning=业务模型调优
|
||||
5.sql-optimization=SQL 调优指南
|
||||
2.sql-execution-plan=SQL 执行计划
|
||||
2.execution-plan-operator=执行计划算子
|
||||
3.distributed-execution-plan=分布式执行计划
|
||||
4.sql-optimization-1=SQL 调优
|
||||
3.monitor-sql-execution-performance=SQL 执行性能监控
|
||||
4.sql-performance-analysis-example=SQL 性能分析示例
|
||||
4.optimizer-statistics=优化器统计信息
|
||||
2.statistics-collection-methods=统计信息收集方式
|
||||
3.statistics-management=统计信息管理
|
||||
5.query-rewrite=查询改写
|
||||
6.query-optimization=查询优化
|
||||
1.access-path=访问路径
|
||||
2.join-algorithm=联接算法
|
||||
7.manage-execution-plans=管理执行计划
|
||||
6.performance-whitepaper=性能测试
|
||||
10.high-data-availability=高可用和容灾
|
||||
1.administrator-guide-flashback=闪回
|
||||
2.backup-and-restoration-management=备份恢复管理
|
||||
3.log-archive=日志归档
|
||||
4.data-backup=数据备份
|
||||
5.cleaning-up-backed-up-data=清理备份
|
||||
6.restore-data=恢复数据
|
||||
11.operation-and-maintenance-management=运维管理
|
||||
2.scale-out-and-scale-in-1=扩容和缩容
|
||||
2.cluster-level-scale-out-and-scale-in=集群级别的扩容和缩容
|
||||
1.scale-out=扩容
|
||||
2.shrink-1=缩容
|
||||
3.scale-in-and-scale-out-of-tenant-resources=租户内资源的扩容和缩容
|
||||
4.monitoring-and-alerting=监控和告警
|
||||
2.monitoring-1=监控
|
||||
3.alert-1=告警
|
||||
5.daily-inspection=日常巡检
|
||||
2.full-link-detection=全链路诊断
|
||||
6.performance-diagnosis=性能诊断
|
||||
8.emergency-response=应急处理
|
||||
3.common-emergency-response=常见应急问题处理
|
||||
1.issues-in-the-hardware-environment=硬件环境导致的问题
|
||||
2.problems-caused-by-capacity-changes=容量变化导致的问题
|
||||
3.other-problems-within-the-cluster=集群内部其他问题
|
||||
12.data-security-management=数据库安全
|
||||
6.data-migration=数据迁移
|
||||
2.migrate-data-from-MySQL-database-to-OceanBase-database=从 MySQL 迁移到 OceanBase 数据库
|
||||
4.migrate-data-from-CSV-file-to-OceanBase-database=从 CSV 文件迁移数据到 OceanBase 数据库
|
||||
7.migrate-data-from-OceanBase-database-to-MySQL=从 OceanBase 迁移到 MySQL 数据库
|
||||
7.reference=参考指南
|
||||
1.oceanbase-database-concepts=系统架构
|
||||
3.multi-tenant-architecture-1=多租户架构
|
||||
5.tenants-and-resource-management-1=租户与资源管理
|
||||
4.database-objects-1=数据库对象
|
||||
1.introduction-to-database-objects-1=数据库对象介绍
|
||||
2.table-1=表
|
||||
2.data-type-3=数据类型
|
||||
3.index-1=索引
|
||||
4.partition-2=分区
|
||||
5.view-2=视图
|
||||
6.system-view-2=系统视图
|
||||
7.data-integrity-1=数据完整性
|
||||
2.integrity-constraint-type-1=完整性约束类型
|
||||
5.distributed-database-objects=分布式数据库对象
|
||||
3.data-partitions-and-replicas=数据分区和分区副本
|
||||
3.partition-replica-type=分区副本类型
|
||||
4.dynamic-scaling=动态扩容和缩容
|
||||
2.scale-in-and-scale-out-of-tenant-resources-1=租户内资源的扩容和缩容
|
||||
6.data-link-1=数据链路
|
||||
2.database-proxy-1=数据库代理
|
||||
7.user-interface-and-query-language=用户接口和查询语言
|
||||
1.SQL=SQL
|
||||
1.sql-introduction=SQL 介绍
|
||||
2.sql-statement-2=SQL 语句
|
||||
5.distributed-execution-plan-2=分布式执行计划
|
||||
2.PL=PL
|
||||
8.transaction-management-1=事务管理
|
||||
1.transaction-2=事务
|
||||
5.transaction-control=事务控制
|
||||
8.distributed-transactions-1=分布式事务
|
||||
2.transaction-concurrency-and-consistency=事务并发和一致性
|
||||
3.concurrency-control-1=并发控制
|
||||
4.transaction-isolation-level=事务隔离级别
|
||||
9.storage-architecture-1=存储架构
|
||||
2.data-storage=数据存储
|
||||
3.dump-and-merge-1=转储和合并
|
||||
6.data-integrity-2=数据完整性
|
||||
10.high-data-reliability-and-availability=数据可靠性和高可用
|
||||
1.high-availability-architecture=高可用架构
|
||||
4.data-protection=数据保护
|
||||
5.backup-and-restoration=备份恢复
|
||||
11.database-security=数据安全
|
||||
12.observer-node-architecture=OBServer 节点架构
|
||||
3.observer-thread-model=observer 线程模型
|
||||
5.memory-management=内存管理
|
||||
2.sql-syntax=SQL 语句
|
||||
1.system-tenants=系统租户
|
||||
2.alter-system=ALTER SYSTEM
|
||||
2.common-tenant-mysql-mode=普通租户
|
||||
1.basic-elements=基本元素
|
||||
1.data-type=数据类型
|
||||
2.numeric-1=数值类型
|
||||
3.date-and-time-types-1=日期时间类型
|
||||
4.string-2=字符类型
|
||||
5.large-object-1=大对象和文本类型
|
||||
8.json-formatted-data-type=JSON 数据类型
|
||||
2.expression-2=表达式
|
||||
3.character-set-and-collation=字符集与字符序
|
||||
4.literal=字面量
|
||||
2.operator=运算符
|
||||
4.functions=函数
|
||||
2.functions-1=单行函数
|
||||
1.date-and-time-functions-1=日期时间函数
|
||||
2.string-functions=字符串函数
|
||||
3.conversion-functions-1=转换函数
|
||||
4.mathematical-functions=数学函数
|
||||
5.comparison-functions=比较函数
|
||||
6.process-control-functions=流程控制函数
|
||||
3.aggregate-function=聚合函数
|
||||
4.analysis-functions-1=分析函数
|
||||
5.encryption-functions=加密函数
|
||||
6.information-functions=信息函数
|
||||
7.json-functions=JSON 函数
|
||||
1.create-a-function-with-json-text=创建 JSON 文本的函数
|
||||
2.a-function-to-search-for-json-text=搜索 JSON 文本的函数
|
||||
3.function-to-modify-json-text=修改 JSON 文本的函数
|
||||
4.function-that-returns-the-json-text-property=返回 JSON 文本属性的函数
|
||||
5.json-functions-1=JSON 工具函数
|
||||
6.json-aggregate-functions=JSON 聚合函数
|
||||
8.other-functions=其它函数
|
||||
5.queries-and-subqueries=查询和子查询
|
||||
6.sql-statement=SQL语句
|
||||
51.SELECT-1-2=SELECT
|
||||
7.ddl-function=DDL 功能
|
||||
3.system-views=系统视图
|
||||
2.dictionary-view-5=字典视图
|
||||
3.performance-view-5=性能视图
|
||||
4.system-variables=系统变量
|
||||
5.system-configuration-items=系统配置项
|
||||
3.cluster-level-configuration-items-1=集群级别配置项
|
||||
4.tenant-level-configuration-items-1=租户级别配置项
|
||||
6.error-codes=错误码
|
||||
8.supporting-tools=生态工具
|
||||
1.ob-admin=ob_admin
|
||||
3.clog=clog
|
||||
2.ob-agent=OBAgent
|
||||
1.about-obagent=关于 OBAgent
|
||||
2.configuration-reference=配置引用
|
||||
3.install-and-deploy-obagent=安装部署
|
||||
4.obagent-metrics=OBAgent 指标
|
||||
4.cdc=CDC
|
||||
2.obcdc=obcdc
|
||||
1.deploy-and-use-obcdc=obcdc 部署和使用
|
||||
2.obcdc-parameters=obcdc 参数说明
|
||||
3.oblogproxy=oblogproxy
|
||||
1.install-and-deploy-oblogproxy=oblogproxy 安装部署
|
||||
4.oblogmsg=oblogmsg
|
||||
10.mysqltest=mysqltest
|
||||
2.use-of-case=case 使用
|
||||
9.releasenotes=版本发布记录
|
||||
99.V4.0=V4.0
|
||||
100.V3.1=V3.1
|
||||
|
|
@ -1,37 +1,37 @@
|
|||
100.oceanbase-database-overview=Overview
|
||||
200.quick-start=Get Started
|
||||
200.Hands-on-for-OceanBase-SQL=Hands on for OceanBase SQL
|
||||
300.Create-a-sample-application=Create a sample application
|
||||
400.Experience-OceanBase-Advanced-Features=Experience OceanBase advanced features
|
||||
100.Experience-Scalable-OLTP=Experience scalable OLTP
|
||||
300.developer-guide=Develop
|
||||
100.client-connects-to-oceanbase-database=Connect to Oceanbase Database with client
|
||||
600.c-application=C application
|
||||
1400.database-connection-pool-configuration-example=Example of Database connection pool configuration
|
||||
200.create-and-manage-database-objects=Create and manage database objects
|
||||
400.data-type=Data type
|
||||
600.create-and-manage-tables=Create and manage tables
|
||||
700.create-and-manage-partition-table=Create and manage partition tables
|
||||
800.create-and-manage-indexes=Create and manage indexes
|
||||
1000.create-and-manage-views=Create and manage views
|
||||
1100.managing-and-creating-sequences=Create and manage sequences
|
||||
300.query=Query
|
||||
800.multi-table-join-queries=Query data from multiple tables
|
||||
900.use-operators-and-functions-in-queries=Use operators and functions in a query
|
||||
1000.execution-plan=Execution plan
|
||||
400.about-dml-statements-and-transactions=DML statements and transactions
|
||||
100.dml-statement=DML statement
|
||||
200.transaction=Transactions
|
||||
500.common-errors-and-solutions-mysql=Common errors and solutions
|
||||
0300.timeout=About timeout
|
||||
0400.user-2=About user
|
||||
0500.table-related-functions=About table
|
||||
0600.constraint-related-functions=About constraint
|
||||
0700.sql-related-commands=About SQL commands
|
||||
400.installation-and-deployment=Deploy
|
||||
200.local-deployment=On-premises deployment
|
||||
400.highly-available-deployment=High availability deployment
|
||||
600.data-migration=Migrate
|
||||
200.migrate-data-from-MySQL-database-to-OceanBase-database=Migrate data from MySQL Database to OceanBase
|
||||
400.migrate-data-from-CSV-file-to-OceanBase-database=Migrate data from CSV-file to OceanBase
|
||||
700.migrate-data-from-OceanBase-database-to-MySQL=Migrate data from OceanBase Database to MySQL
|
||||
1.oceanbase-database-overview=Overview
|
||||
2.quick-start=Get Started
|
||||
2.Hands-on-for-OceanBase-SQL=Hands on for OceanBase SQL
|
||||
3.Create-a-sample-application=Create a sample application
|
||||
4.Experience-OceanBase-Advanced-Features=Experience OceanBase advanced features
|
||||
1.Experience-Scalable-OLTP=Experience scalable OLTP
|
||||
3.developer-guide=Develop
|
||||
1.client-connects-to-oceanbase-database=Connect to Oceanbase Database with client
|
||||
6.c-application=C application
|
||||
14.database-connection-pool-configuration-example=Example of Database connection pool configuration
|
||||
2.create-and-manage-database-objects=Create and manage database objects
|
||||
4.data-type=Data type
|
||||
6.create-and-manage-tables=Create and manage tables
|
||||
7.create-and-manage-partition-table=Create and manage partition tables
|
||||
8.create-and-manage-indexes=Create and manage indexes
|
||||
10.create-and-manage-views=Create and manage views
|
||||
11.managing-and-creating-sequences=Create and manage sequences
|
||||
3.query=Query
|
||||
8.multi-table-join-queries=Query data from multiple tables
|
||||
9.use-operators-and-functions-in-queries=Use operators and functions in a query
|
||||
10.execution-plan=Execution plan
|
||||
4.about-dml-statements-and-transactions=DML statements and transactions
|
||||
1.dml-statement=DML statement
|
||||
2.transaction=Transactions
|
||||
5.common-errors-and-solutions-mysql=Common errors and solutions
|
||||
03.timeout=About timeout
|
||||
04.user-2=About user
|
||||
05.table-related-functions=About table
|
||||
06.constraint-related-functions=About constraint
|
||||
07.sql-related-commands=About SQL commands
|
||||
4.installation-and-deployment=Deploy
|
||||
2.local-deployment=On-premises deployment
|
||||
4.highly-available-deployment=High availability deployment
|
||||
6.data-migration=Migrate
|
||||
2.migrate-data-from-MySQL-database-to-OceanBase-database=Migrate data from MySQL Database to OceanBase
|
||||
4.migrate-data-from-CSV-file-to-OceanBase-database=Migrate data from CSV-file to OceanBase
|
||||
7.migrate-data-from-OceanBase-database-to-MySQL=Migrate data from OceanBase Database to MySQL
|
||||
|
|
@ -0,0 +1,13 @@
|
|||
# Document overview
|
||||
|
||||
OceanBase is an enterprise-grade open source distributed SQL database. It supports transparent scalability, distributed transaction, multi-tenancy, and is highly compatible with MySQL
|
||||
|
||||
|
||||
|
||||
| Get started | Develop | Migrate |
|
||||
|----------------------------|-------------------------------------|-------------------------------------|
|
||||
| [OceanBase Overview](1.oceanbase-database-overview/1.what-is-oceanbase-database.md) | [Connect to OceanBase via OBClient](3.developer-guide/1.client-connects-to-oceanbase-database/3.connect-oceanbase-tenants-through-obclient.md) | [Use Canal to synchronize MySQL data to OceanBase Database in real time](6.data-migration/2.migrate-data-from-MySQL-database-to-OceanBase-database/7.use-canal-to-synchronize-MySQL-data-to-OceanBase-database-in-real-time.md) |
|
||||
| [Quick experience](2.quick-start/1.Quickly-experience-OceanBase.md) | [Manage database objects](3.developer-guide/2.create-and-manage-database-objects/1.about-ddl-statements.md) |[Use DBCAT to migrate MySQL table schemas to OceanBase Database](6.data-migration/2.migrate-data-from-MySQL-database-to-OceanBase-database/10.use-DBCAT-to-migrate-MySQL-table-structure-to-OceanBase-database.md) |
|
||||
| [Basic SQL operations](2.quick-start/2.Hands-on-for-OceanBase-SQL/2.SQL-operations.md) | [Write data](3.developer-guide/4.about-dml-statements-and-transactions/1.dml-statement/1.about-dml-statements.md) |[Migrate MySQL table schemas to OceanBase Database by using mysqldump](6.data-migration/2.migrate-data-from-MySQL-database-to-OceanBase-database/12.use-MySQLDump-to-migrate-MySQL-table-structure-to-OceanBase-database.md) |
|
||||
| [Connect to OceanBase](2.quick-start/3.Create-a-sample-application/1.Connect-a-Python-application-to-OceanBase-Database.md) |[Query data](3.developer-guide/3.query/1.about-queries.md) |[Migrate MySQL table data to OceanBase Database by using mysqldump](6.data-migration/2.migrate-data-from-MySQL-database-to-OceanBase-database/13.use-MySQLDump-to-migrate-MySQL-table-data-to-OceanBase-database.md) |
|
||||
| [Run the TPC-C benchmark test on OceanBase Database](2.quick-start/4.Experience-OceanBase-Advanced-Features/1.Experience-Scalable-OLTP/1.TPC-C-test-on-OceanBase.md) |[Transaction](3.developer-guide/4.about-dml-statements-and-transactions/2.transaction/1.about-transactional-control-statements.md) | [Use DataX to migrate MySQL data to OceanBase Database](6.data-migration/2.migrate-data-from-MySQL-database-to-OceanBase-database/9.migrate-MySQL-data-to-OceanBase-database-using-dataX.md) |
|
||||
|
|
@ -1,13 +0,0 @@
|
|||
# Document overview
|
||||
|
||||
OceanBase is an enterprise-grade open source distributed SQL database. It supports transparent scalability, distributed transaction, multi-tenancy, and is highly compatible with MySQL
|
||||
|
||||
|
||||
|
||||
| Get started | Develop | Migrate |
|
||||
|----------------------------|-------------------------------------|-------------------------------------|
|
||||
| [OceanBase Overview](100.oceanbase-database-overview/100.what-is-oceanbase-database.md) | [Connect to OceanBase via OBClient](300.developer-guide/100.client-connects-to-oceanbase-database/300.connect-oceanbase-tenants-through-obclient.md) | [Use Canal to synchronize MySQL data to OceanBase Database in real time](600.data-migration/200.migrate-data-from-MySQL-database-to-OceanBase-database/700.use-canal-to-synchronize-MySQL-data-to-OceanBase-database-in-real-time.md) |
|
||||
| [Quick experience](200.quick-start/100.Quickly-experience-OceanBase.md) | [Manage database objects](300.developer-guide/200.create-and-manage-database-objects/100.about-ddl-statements.md) |[Use DBCAT to migrate MySQL table schemas to OceanBase Database](600.data-migration/200.migrate-data-from-MySQL-database-to-OceanBase-database/1000.use-DBCAT-to-migrate-MySQL-table-structure-to-OceanBase-database.md) |
|
||||
| [Basic SQL operations](200.quick-start/200.Hands-on-for-OceanBase-SQL/200.SQL-operations.md) | [Write data](300.developer-guide/400.about-dml-statements-and-transactions/100.dml-statement/100.about-dml-statements.md) |[Migrate MySQL table schemas to OceanBase Database by using mysqldump](600.data-migration/200.migrate-data-from-MySQL-database-to-OceanBase-database/1200.use-MySQLDump-to-migrate-MySQL-table-structure-to-OceanBase-database.md) |
|
||||
| [Connect to OceanBase](200.quick-start/300.Create-a-sample-application/100.Connect-a-Python-application-to-OceanBase-Database.md) |[Query data](300.developer-guide/300.query/100.about-queries.md) |[Migrate MySQL table data to OceanBase Database by using mysqldump](600.data-migration/200.migrate-data-from-MySQL-database-to-OceanBase-database/1300.use-MySQLDump-to-migrate-MySQL-table-data-to-OceanBase-database.md) |
|
||||
| [Run the TPC-C benchmark test on OceanBase Database](200.quick-start/400.Experience-OceanBase-Advanced-Features/100.Experience-Scalable-OLTP/100.TPC-C-test-on-OceanBase.md) |[Transaction](300.developer-guide/400.about-dml-statements-and-transactions/200.transaction/100.about-transactional-control-statements.md) | [Use DataX to migrate MySQL data to OceanBase Database](600.data-migration/200.migrate-data-from-MySQL-database-to-OceanBase-database/900.migrate-MySQL-data-to-OceanBase-database-using-dataX.md) |
|
||||
|
|
@ -0,0 +1,35 @@
|
|||
# Overview
|
||||
|
||||
OceanBase Database is an enterprise-grade distributed database management system (DBMS) with excellent transactional and analytical processing capabilities. It is used in various business scenarios and has a complete peripheral support system.
|
||||
|
||||
As a proprietary DBMS, OceanBase Database supports both hybrid transactional and analytical processing (HTAP) with a single architecture, which combines the high scalability of a distributed system and the high efficiency of a centralized system.
|
||||
|
||||
OceanBase Database provides the same atomicity, consistency, isolation, and durability (ACID) capability in both centralized and distributed modes. It uses the Paxos protocol-based multi-replica synchronization algorithm, which guarantees consistency among multiple data replicas. In case a hardware failure occurs, OceanBase Database can quickly perform a replica switchover to ensure the availability of database services. In addition, it is compatible with MySQL syntaxes, making it easy to migrate your data from a MySQL database to an OceanBase database. Moreover, OceanBase Database uses code-based compression to significantly reduce storage space required.
|
||||
|
||||
OceanBase Database ranks No.1 in the TPC-C benchmark test with a performance result of 707.35 million tpmC and ranks No.2 in the TPC-H benchmark test with a performance result of 15.26 million QphH@30,000 GB.
|
||||
|
||||
OceanBase Database has supported the stable and efficient operation of core business systems of customers in various industries, such as banking, insurance, transportation, and telecommunications.
|
||||
|
||||
## Core features
|
||||
|
||||
OceanBase Database provides the following features:
|
||||
|
||||
* Higher stability
|
||||
|
||||
OceanBase Database has been supporting the Double 11 Shopping Festival (the biggest online shopping festival in the world) for 9 consecutive years and has been tested in core systems of Ant Group with more than a million servers. It supports single-server failure recovery, cross-city cross-IDC disaster recovery, and multi-replica data storage. OceanBase has innovatively launched a new city-level disaster recovery standard of "Five IDCs across Three Cities". OceanBase can achieve Recovery Point Objective (RPO) = 0, Recovery Time Objective (RTO) ≤ 8 seconds, which reaches the financial-grade disaster recovery standard level 6.
|
||||
|
||||
* Stronger performance
|
||||
|
||||
OceanBase Database supports online transaction processing (OLTP) and online analytical processing (OLAP), even in the case of massive data. OLTP and OLAP resources are isolated from each other and can be linearly scaled. OceanBase Database achieves a performance result of 707.35 million tpmC in the TPC-C benchmark test and a performance result of 15.26 million QphH@30,000 GB in the TPC-H benchmark test.
|
||||
|
||||
* Improved KV query performance
|
||||
|
||||
OceanBase Database has the OBKV capability, which provides NoSQL capabilities for the HBase and Table models. The performance of OBKV is exponentially improved with secondary indexing, which avoids HBase performance jitters.
|
||||
|
||||
* Lower storage and O&M costs
|
||||
|
||||
OceanBase Database can be deployed on PC servers with low-end SSDs. Its high compression ratio reduces storage costs, and its decentralized multi-tenant architecture significantly improves the utilization of compute resources. It also supports popular tools in the database ecosystem, such as Prometheus and Canal, which makes O&M easier.
|
||||
|
||||
* Compatible with MySQL open source ecosystem
|
||||
|
||||
OceanBase Database is highly compatible with the MySQL ecosystem and provides modular tools that allow users to manage the entire lifecycle of a database, including development, debugging, production, O&M, and data transmission.
|
||||
|
|
@ -1,48 +0,0 @@
|
|||
# Overview
|
||||
|
||||
OceanBase Database is an enterprise-grade distributed database management system (DBMS) with excellent transactional and analytical processing capabilities. It is used in various business scenarios and has a complete peripheral support system.
|
||||
|
||||
As a proprietary DBMS, OceanBase Database supports both hybrid transactional and analytical processing (HTAP) with a single architecture, which combines the high scalability of a distributed system and the high efficiency of a centralized system.
|
||||
|
||||
OceanBase Database provides the same atomicity, consistency, isolation, and durability (ACID) capability in both centralized and distributed modes. It uses the Paxos protocol-based multi-replica synchronization algorithm, which guarantees consistency among multiple data replicas. In case a hardware failure occurs, OceanBase Database can quickly perform a replica switchover to ensure the availability of database services. In addition, it is compatible with MySQL syntaxes, making it easy to migrate your data from a MySQL database to an OceanBase database. Moreover, OceanBase Database uses code-based compression to significantly reduce storage space required.
|
||||
|
||||
OceanBase Database ranks No.1 in the TPC-C benchmark test with a performance result of 707.35 million tpmC and ranks No.2 in the TPC-H benchmark test with a performance result of 15.26 million QphH@30,000 GB.
|
||||
|
||||
OceanBase Database has supported the stable and efficient operation of core business systems of customers in various industries, such as banking, insurance, transportation, and telecommunications.
|
||||
|
||||
## Core features
|
||||
|
||||
OceanBase Database provides the following features:
|
||||
|
||||
### High availability
|
||||
|
||||
OceanBase Database implements a unique disaster recovery solution with five IDCs across three regions, which sets forth a new standard for lossless disaster recovery in the financial industry. OceanBase Database supports multi-active IDCs deployed across multiple regions for zone- and geo-disaster recovery, which meets the Level 6 disaster recovery requirements of the financial industry with a recovery point objective (RPO) of 0 and a recovery time objective (RTO) of less than 8 seconds.
|
||||
|
||||
### High compatibility
|
||||
|
||||
OceanBase Database is highly compatible with most general features of MySQL, and supports advanced features such as procedural language and triggers. OceanBase Migration Service (OMS), an automatic migration tool, is provided to support reverse synchronization to ensure data migration security when a core system is migrated to OceanBase Database in key industries such as finance, public governance, and communication service.
|
||||
|
||||
### Scaling out
|
||||
|
||||
OceanBase Database supports rapid transparent horizontal scaling in response to business fluctuations, and achieves high performance based on a quasi-memory transaction processing architecture. You can deploy thousands of nodes in an OceanBase cluster, where the maximum data volume can exceed 3 PB and a single table can contain trillions of rows.
|
||||
|
||||
### Low costs
|
||||
|
||||
OceanBase Database adopts a storage engine based on the log-structured merge-tree (LSM-tree), which can achieve a high compression ratio and reduce storage costs by 70% to 90%. OceanBase Database also supports native multitenancy, which means that the same cluster can serve multiple business lines with the data of one tenant isolated from that of others. These features reduce deployment and O&M costs.
|
||||
|
||||
### Real-time HTAP
|
||||
|
||||
OceanBase Database uses the same database engine to perform online real-time transactions and real-time analysis on the same set of data. Multiple replicas of the same set of data can be stored in different forms for different purposes. This fundamentally ensures data consistency.
|
||||
|
||||
### Security and reliability
|
||||
|
||||
The OceanBase team has been independently developing OceanBase Database for 12 years and has full control over its source code. The integrated architecture of OceanBase Database has reliably supported large-scale financial core systems for nine years. In addition to a sound roles and permissions management system, OceanBase Database also meets the Level 3 requirements of Multi-Level Protection Scheme (MLPS).
|
||||
|
||||
### Complete ownership of intellectual property rights
|
||||
|
||||
OceanBase Database is developed independently by Ant Group. It is not based on open-source databases such as MySQL or PostgreSQL. OceanBase Database is autonomous, controllable, and free from the technical limits of open-source databases.
|
||||
|
||||
|
||||
<!-- ### Compatibility with products from Chinese manufacturers
|
||||
|
||||
OceanBase Database supports products from Chinese manufacturers in full stack. OceanBase Database can work on physical servers from Chinese manufacturers including Sugon H620 series, TaiShan 200 series, and Great Wall Optimus DF720. OceanBase Database is also adaptive to CPUs including Hygon 7185/7280, Kunpeng 920, and FeiTeng 2000+. In addition, OceanBase Database supports operating systems from Chinese manufacturers, such as Kylin V4, Kylin V10, and UOS V20. OceanBase Database is also adaptive to upper-layer middleware including TongWeb V7.0 and Apusic Application Server V9.0. -->
|
||||
|
|
@ -29,7 +29,7 @@ OceanBase Database allows you to address this issue by using any of the followin
|
|||
To enable write throttling when the tenant memory usage reaches 80% and ensure that the remaining memory is sufficient for data writing for 1 hour, log on to the database as the tenant administrator and execute the following statements:
|
||||
|
||||
```sql
|
||||
obclient -h127.0.0.1 -P2881 -uroot@test -Doceanbase -p******
|
||||
obclient -h127.0.0.1 -P2881 -uroot@test -Doceanbase -p
|
||||
|
||||
ALTER SYSTEM SET writing_throttling_trigger_percentage = 80;
|
||||
ALTER SYSTEM SET writing_throttling_maximum_duration = '1h';
|
||||
|
|
@ -42,7 +42,7 @@ OceanBase Database allows you to address this issue by using any of the followin
|
|||
1. Log on to the sys tenant of the OceanBase cluster as the administrator and execute the following SQL statement to confirm the unit_config name used by the current tenant.
|
||||
|
||||
```sql
|
||||
obclient -h127.0.0.1 -P2881 -uroot@sys -Doceanbase -p******
|
||||
obclient -h127.0.0.1 -P2881 -uroot@sys -Doceanbase -p
|
||||
|
||||
SELECT * FROM oceanbase.DBA_OB_UNIT_CONFIGS\G ##The sys_unit_config parameter is a parameter of the sys tenant and you do not need to modify it. In this example, the test tenant is used and its unit_config name is test_unit.
|
||||
```
|
||||
|
|
@ -64,7 +64,7 @@ OceanBase Database allows you to address this issue by using any of the followin
|
|||
Log on to the sys tenant as the root user and execute the following statements:
|
||||
|
||||
```SQL
|
||||
obclient -h127.0.0.1 -P2881 -uroot@sys -Doceanbase -p******
|
||||
obclient -h127.0.0.1 -P2881 -uroot@sys -Doceanbase -p
|
||||
|
||||
ALTER SYSTEM SET freeze_trigger_percentage=40;
|
||||
ALTER SYSTEM SET memstore_limit_percentage=70;
|
||||
|
|
@ -654,7 +654,7 @@ Query OK, 0 rows affected
|
|||
obclient> exit;
|
||||
Bye
|
||||
|
||||
[user@host ~]$obclient -h10.10.10.1 -u******@obmysql#obdemo -P2883 -p****** TPCC
|
||||
[user@host ~]$obclient -h10.10.10.1 -u******@obmysql#obdemo -P2883 -p**1*** TPCC
|
||||
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
|
||||
|
||||
obclient> SELECT * FROM t_insert;
|
||||
|
|
@ -73,7 +73,7 @@ connection = DriverManager.getConnection("jdbc:mysql://{hostname}:{port}/{dbname
|
|||
|
||||
* **password**: the password of the connection account.
|
||||
|
||||
Example: `jdbc:mysql://172.30.xx.xx:2883/test?user=r***&password=******`
|
||||
Example: `jdbc:mysql://172.30.xx.xx:2883/test?user=r***&password=***1**`
|
||||
|
||||
After you edit the code, run the following command to compile and execute the file. If `true` is returned, the database is connected.
|
||||
|
||||
|
|
@ -16,7 +16,7 @@ Before you install OceanBase Connector/C, make sure that you have set up the bas
|
|||
|
||||
Obtain the RPM packages of OBClient and OceanBase Connector/C, which is also known as `libobclient`.
|
||||
|
||||
You need to visit the image repository and find the installation packages based on your system version. For more information, see [Software and hardware requirements](../../400.installation-and-deployment/200.local-deployment/100.requirements-for-software-and-hardware.md).
|
||||
You need to visit the image repository and find the installation packages based on your system version. For more information, see [Software and hardware requirements](../../4.installation-and-deployment/2.local-deployment/1.requirements-for-software-and-hardware.md).
|
||||
|
||||
1. Install `libobclient`.
|
||||
|
||||
|
|
@ -163,7 +163,7 @@ int main(int argc, char** argv)
|
|||
MYSQL *mysql = mysql_init(NULL);
|
||||
char* host_name = "172.xx.xx.xx";//set your mysql host
|
||||
char* user_name = "r***"; //set your user_name
|
||||
char* password = "******"; //set your password
|
||||
char* password = "***1**"; //set your password
|
||||
char* db_name = "test"; //set your databasename
|
||||
int port_num = 2883; //set your mysql port
|
||||
char* socket_name = NULL;
|
||||
|
|
@ -34,8 +34,8 @@ The TPC-C benchmark test involves the following five types of transactions:
|
|||
|
||||
### OceanBase cluster
|
||||
|
||||
You can observe the performance of OceanBase Database in different ways based on the type of your OceanBase cluster. If you have created a single-node OceanBase cluster, you can observe the performance of OceanBase Database in standalone deployment mode. For more information about how to create an OceanBase cluster, see Quick Start. To experience the scalable OLTP capability of the distributed architecture of OceanBase Database, we recommend that you create an OceanBase cluster with at least three nodes. For more information, see [Installation and deployment](../../../400.installation-and-deployment/100.deployment-overview.md).
|
||||
In this example, the tenant name is `test`. You can create your own tenant. For more information, see [Experience the multitenancy feature](../400.Experience-the-multi-tenancy-feature.md).
|
||||
You can observe the performance of OceanBase Database in different ways based on the type of your OceanBase cluster. If you have created a single-node OceanBase cluster, you can observe the performance of OceanBase Database in standalone deployment mode. For more information about how to create an OceanBase cluster, see Quick Start. To experience the scalable OLTP capability of the distributed architecture of OceanBase Database, we recommend that you create an OceanBase cluster with at least three nodes. For more information, see [Installation and deployment](../../../4.installation-and-deployment/1.deployment-overview.md).
|
||||
In this example, the tenant name is `test`. You can create your own tenant. For more information, see [Experience the multitenancy feature](../4.Experience-the-multi-tenancy-feature.md).
|
||||
|
||||
### Install BenchmarkSQL
|
||||
|
||||
|
|
@ -56,7 +56,7 @@ db=oracle
|
|||
driver=com.mysql.cj.jdbc.Driver
|
||||
conn=jdbc:oceanbase://127.0.0.1:2881/tpccdb?useUnicode=true&characterEncoding=utf-8&rewriteBatchedStatements=true&allowMultiQueries=true
|
||||
user=root@test
|
||||
password=******
|
||||
password=root
|
||||
|
||||
warehouses=10
|
||||
loadWorkers=2
|
||||
|
|
@ -38,8 +38,8 @@ import threading
|
|||
# database connection info
|
||||
config = {
|
||||
'user': 'root@test',
|
||||
'password': '******',
|
||||
'host': 'xxx.xxx.xxx.xxx',
|
||||
'password': 'root',
|
||||
'host': '172.19.81.183',
|
||||
'port': 2881,
|
||||
'database': 'test'
|
||||
}
|
||||
|
|
@ -162,4 +162,3 @@ This example describes only concurrent single-row updates. The ELR feature of Oc
|
|||
The ELR feature of OceanBase Database also applies to multi-region deployment scenarios with high network latency. For example, the execution of a single transaction requires 30 ms in the default scenario. If you enable the ELR feature and concurrent execution, the TPS can increase by about 100 times.
|
||||
|
||||
The log protocol of OceanBase Database is based on multi-Paxos, with the optimized two-phase commit (2PC) process. Therefore, after the ELR feature is enabled, transaction consistency can still be ensured in the case of server restart or leader switchover. You can try these tests to experience the ELR feature.
|
||||
|
||||
|
|
@ -86,7 +86,7 @@ If the preceding statement succeeds, you have created two tenants in the same cl
|
|||
Log on to tenant1 and create a test table.
|
||||
|
||||
```sql
|
||||
obclient -hXXX.XX.XXX.106 -P2883 -uroot@tenant1#ob_test -p******
|
||||
obclient -hXXX.XX.XXX.106 -P2883 -uroot@tenant1#ob_test -p
|
||||
obclient [(none)]> show databases;
|
||||
+--------------------+
|
||||
| Database |
|
||||
|
|
@ -115,7 +115,7 @@ obclient [test]> show tables;
|
|||
Log on to tenant2 and query the test database.
|
||||
|
||||
```sql
|
||||
obclient -hXXX.XX.XXX.106 -P2883 -uroot@tenant2#ob_test -p******
|
||||
obclient -hXXX.XX.XXX.106 -P2883 -uroot@tenant2#ob_test -p
|
||||
|
||||
obclient [(none)]> show databases;
|
||||
+--------------------+
|
||||
|
|
@ -27,7 +27,7 @@ static {
|
|||
map.put("url", "jdbc:oceanbase://10.100.xxx.xxx:18815/test");
|
||||
map.put("driverClassName", "com.alipay.oceanbase.jdbc.Driver");
|
||||
map.put("username", "admin@mysql");
|
||||
map.put("password", "******");
|
||||
map.put("password", "admin");
|
||||
try {
|
||||
Class.forName(map.get("driverClassName"));
|
||||
jdbcTemplate = new JdbcTemplate(DruidDataSourceFactory.createDataSource(map));
|
||||
|
|
@ -132,7 +132,7 @@ The following example shows the content of a configuration file:
|
|||
jdbc.driver=com.alipay.oceanbase.jdbc.Driver
|
||||
jdbc.url=jdbc:oceanbase://10.100.xxx.xxx:18815/test
|
||||
jdbc.username=admin
|
||||
jdbc.password=******
|
||||
jdbc.password=admin
|
||||
database.dialect=MYSQL
|
||||
dbcp.maxIdle=5
|
||||
dbcp.maxActive=40
|
||||
|
|
@ -164,7 +164,7 @@ Configure the data source and JPA part in the configuration file as follows:
|
|||
```java
|
||||
spring.datasource.url=jdbc:oceanbase://10.100.xxx.xxx:18815/test
|
||||
spring.datasource.username=admin@mysql
|
||||
spring.datasource.password=******
|
||||
spring.datasource.password=admin
|
||||
spring.datasource.driver-class-name=com.alipay.oceanbase.jdbc.Driver
|
||||
|
||||
spring.jpa.hibernate.ddl-auto=update
|
||||
|
|
@ -36,7 +36,7 @@ The following example shows the content of a configuration file:
|
|||
<property name="driver" value="com.alipay.oceanbase.jdbc.Driver"/>
|
||||
<property name="url" value="jdbc:oceanbase://10.100.xxx.xxx:18817/test?useUnicode=true&characterEncoding=utf-8&useServerPrepStmts=false&useCursorFetch=true"/>
|
||||
<property name="username" value="admin@mysql"/>
|
||||
<property name="password" value="******"/>
|
||||
<property name="password" value="admin"/>
|
||||
</dataSource>
|
||||
</environment>
|
||||
</environments>
|
||||
|
|
@ -26,7 +26,7 @@ This topic describes how to configure dependencies and configuration files for a
|
|||
```dart
|
||||
jdbcUrl=jdbc:oceanbase://10.100.xxx.xxx:18817/test?useSSL=false&useServerPrepStmts=true&serverTimezone=UTC
|
||||
username=admin@mysql
|
||||
password=******
|
||||
password=admin
|
||||
dataSource.cachePrepStmts=true
|
||||
dataSource.prepStmtCacheSize=250
|
||||
dataSource.prepStmtCacheSqlLimit=2048
|
||||
|
|
@ -46,7 +46,7 @@ url=jdbc:oceanbase://10.100.xxx.xxx:18817/test?useSSL=false&useServerPrepStmts=t
|
|||
#Username
|
||||
username=admin@mysql
|
||||
#Password
|
||||
password=******
|
||||
password=admin
|
||||
#Number of initial connections
|
||||
initialSize=30
|
||||
#Maximum number of active connections
|
||||
|
|
@ -145,7 +145,7 @@ public class DBConn {
|
|||
Class.forName("com.alipay.oceanbase.jdbc.Driver");
|
||||
DriverManager.registerDriver(new com.alipay.oceanbase.jdbc.Driver());
|
||||
String dbUrl = "jdbc:oceanbase://10.100.xxx.xxx:18817/test?useSSL=false&useServerPrepStmts=true&serverTimezone=UTC";
|
||||
conn = DriverManager.getConnection(dbUrl, "admin@mysql", "******");
|
||||
conn = DriverManager.getConnection(dbUrl, "admin@mysql", "admin");
|
||||
// System.out.println("========Database connected========");
|
||||
} catch (Exception e) {
|
||||
e.printStackTrace();
|
||||
|
|
@ -139,7 +139,7 @@ Hibernate configuration file:
|
|||
<property name="connection.driver_class">com.alipay.oceanbase.jdbc.Driver</property>
|
||||
<property name="connection.url">jdbc:oceanbase://10.100.xxx.xxx:18815/test</property>
|
||||
<property name="connection.username">admin@mysql</property>
|
||||
<property name="connection.password">******</property>
|
||||
<property name="connection.password">admin</property>
|
||||
|
||||
<!-- Optional configuration -->
|
||||
|
||||
|
|
@ -87,12 +87,12 @@ Before you connect to an OceanBase database by using a MySQL client, make sure t
|
|||
Connect to OceanBase Database by using a MySQL client
|
||||
|
||||
```sql
|
||||
$mysql -h10.10.10.1 -u****@obmysql#obdemo -P2883 -p****** -c -A oceanbase
|
||||
$mysql -h10.10.10.1 -u****@obmysql#obdemo -P2883 -p**1*** -c -A oceanbase
|
||||
Welcome to the MariaDB monitor. Commands end with ; or \g.
|
||||
Your MySQL connection id is 5751
|
||||
Server version: 5.6.25 OceanBase 4.0.0 (r10100032022041510-a09d3134c10665f03fd56d7f8bdd413b2b771977) (Built Apr 15 2022 02:16:22)
|
||||
|
||||
<...>
|
||||
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
|
||||
|
||||
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
|
||||
|
||||
|
|
@ -53,13 +53,13 @@ The OBClient application is downloaded and installed. You can install the OBClie
|
|||
Examples:
|
||||
|
||||
```sql
|
||||
obclient -h10.10.10.1 -u****@obtenant#obdemo -P2883 -p****** -c -A oceanbase
|
||||
obclient -h10.10.10.1 -u****@obtenant#obdemo -P2883 -p**1*** -c -A oceanbase
|
||||
```
|
||||
|
||||
or
|
||||
|
||||
```sql
|
||||
obclient -h10.10.10.1 -uobdemo:obtenant:**** -P2883 -p****** -c -A oceanbase
|
||||
obclient -h10.10.10.1 -uobdemo:obtenant:**** -P2883 -p**1*** -c -A oceanbase
|
||||
```
|
||||
|
||||
* To directly connect to the MySQL tenant, run the following command:
|
||||
|
|
@ -89,7 +89,7 @@ The OBClient application is downloaded and installed. You can install the OBClie
|
|||
Example:
|
||||
|
||||
```sql
|
||||
obclient -h10.10.10.1 -u******@obtenant -P2881 -p****** -c -A oceanbase
|
||||
obclient -h10.10.10.1 -u******@obtenant -P2881 -p**1*** -c -A oceanbase
|
||||
```
|
||||
|
||||
3. After the connection is established, the following command-line prompt is displayed by default:
|
||||
|
|
@ -105,7 +105,7 @@ The OBClient application is downloaded and installed. You can install the OBClie
|
|||
Connect to OceanBase Database by using OBClient
|
||||
|
||||
```sql
|
||||
$obclient -h10.10.10.1 -u****@obmysql#obdemo -P2883 -p****** -c -A sys
|
||||
$obclient -h10.10.10.1 -u****@obmysql#obdemo -P2883 -p**1*** -c -A sys
|
||||
Welcome to the OceanBase. Commands end with ; or \g.
|
||||
Your OceanBase connection id is 5751
|
||||
Server version: 5.6.25 OceanBase 4.0.0 (r10100032022041510-a09d3134c10665f03fd56d7f8bdd413b2b771977) (Built Apr 15 2022 02:16:22)
|
||||
|
|
@ -16,7 +16,7 @@ Before you install OceanBase Connector/C, make sure that you have set up the bas
|
|||
|
||||
You must obtain the installation package of OBClient and OceanBase Connector/C, which is also known as `libobclient`.
|
||||
|
||||
Find the required installation packages in the image repository based on your system version and download the installation packages. For more information, see **Software resources** in [Software and hardware requirements](../../../400.installation-and-deployment/200.local-deployment/100.requirements-for-software-and-hardware.md).
|
||||
Find the required installation packages in the image repository based on your system version and download the installation packages. For more information, see **Software resources** in [Software and hardware requirements](../../../4.installation-and-deployment/2.local-deployment/1.requirements-for-software-and-hardware.md).
|
||||
|
||||
1. Install OceanBase Connector/C.
|
||||
|
||||
|
|
@ -163,7 +163,7 @@ int main(int argc, char** argv)
|
|||
MYSQL *mysql = mysql_init(NULL);
|
||||
char* host_name = "172.xx.xx.xx";// Set your mysql host.
|
||||
char* user_name = "r***"; // Set your username.
|
||||
char* password = "******"; // Set your password.
|
||||
char* password = "***1**"; // Set your password.
|
||||
char* db_name = "test"; // Set your database name.
|
||||
int port_num = 2883; // Set your MySQL port number.
|
||||
char* socket_name = NULL;
|
||||
|
|
@ -63,7 +63,7 @@ func main() {
|
|||
}
|
||||
|
||||
func select_all() {
|
||||
conn := "root:******@tcp(127.0.0.1:2881)/testdb"
|
||||
conn := "root:@tcp(127.0.0.1:2881)/testdb"
|
||||
db, err := sql.Open("mysql", conn)
|
||||
if err != nil {
|
||||
log.Fatal(err)
|
||||
|
|
@ -116,7 +116,7 @@ conn := "{username}:{password}@tcp({hostname}:{port})/{dbname}"
|
|||
|
||||
* **dbname**: the name of the database to be accessed.
|
||||
|
||||
Example: `conn := "root:******@tcp(127.0.0.1:2881)/testdb"`
|
||||
Example: `conn := "root:@tcp(127.0.0.1:2881)/testdb"`
|
||||
|
||||
After you edit the code, run the following command:
|
||||
|
||||
|
|
@ -58,7 +58,7 @@ Server = 127.0.0.1
|
|||
Database = testdb
|
||||
Port = 2881
|
||||
User = root
|
||||
Password = ******
|
||||
Password =
|
||||
CHARSET = UTF8
|
||||
```
|
||||
|
||||
|
|
@ -47,7 +47,7 @@ spring:
|
|||
url: jdbc:oceanbase://10.100.xxx.xxx:18815/test
|
||||
driver-class-name: com.alipay.oceanbase.jdbc.Driver
|
||||
username: admin@mysql
|
||||
password: ******
|
||||
password: admin
|
||||
jpa:
|
||||
hibernate:
|
||||
ddl-auto: update
|
||||
|
|
@ -56,10 +56,10 @@ SQL syntax:
|
|||
obclient> ALTER USER username IDENTIFIED BY 'password';
|
||||
```
|
||||
|
||||
Example for changing the password of sqluser01 to `******`:
|
||||
Example for changing the password of sqluser01 to `***1**`:
|
||||
|
||||
```sql
|
||||
obclient> ALTER USER sqluser01 IDENTIFIED BY ******;
|
||||
obclient> ALTER USER sqluser01 IDENTIFIED BY ***1**;
|
||||
```
|
||||
|
||||
### Change the password of a user by using the SET PASSWORD statement
|
||||
|
|
@ -78,9 +78,9 @@ Notes:
|
|||
|
||||
* If the `FOR user` clause is specified, this statement changes the password of the specified user. To change the password of a specified user, you must have the global `CREATE USER` privilege.
|
||||
|
||||
Example for changing the password of `sqluser01` to `******`:
|
||||
Example for changing the password of `sqluser01` to `***1**`:
|
||||
|
||||
```sql
|
||||
obclient> SET PASSWORD FOR sqluser01 = password('******');
|
||||
obclient> SET PASSWORD FOR sqluser01 = password('***1**');
|
||||
Query OK, 0 rows affected
|
||||
```
|
||||
|
|
@ -30,6 +30,8 @@ table_definition:
|
|||
REFERENCES reference_definition
|
||||
[match_action][opt_reference_option_list]
|
||||
| {INDEX | KEY} [index_name] index_desc
|
||||
| FULLTEXT [INDEX | KEY]
|
||||
[index_name] fulltext_index_desc
|
||||
|
||||
column_definition_list:
|
||||
column_definition [, column_definition ...]
|
||||
|
|
@ -54,6 +56,9 @@ opt_reference_option_list:
|
|||
reference_option:
|
||||
ON {DELETE | UPDATE} {RESTRICT | CASCADE | SET NULL | NO ACTION | SET DEFAULT}
|
||||
|
||||
fulltext_index_desc:
|
||||
(column_desc_list) CTXCAT(column_desc_list) [index_option_list]
|
||||
|
||||
column_desc_list:
|
||||
column_desc [, column_desc ...]
|
||||
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
# About table structure modification
|
||||
|
||||
This topic describes how to **rename a table**, **rename a column**, **modify a column type**, **rename a column and change the column type**, **change a normal column to an auto-increment column**, **add a column**, **delete a column**, **add a primary key**, **modify a primary key**, **delete a primary ke**y, **add a foreign key**, **delete a foreign key**, **add a CHECK constraint**, and **modify a table partition**.
|
||||
This topic describes how to [rename a table](#example%201-1%20rename%20a%20table), [rename a column](#example%201-2%20rename%20a%20column), [modify a column type](#example%201-3%20change%20the%20type%20of%20a%20column), [rename a column and change the column type](#example%201-4%20rename%20a%20column%20and%20change%20the%20column%20type%20at%20the%20same%20time), [change a normal column to an auto-increment column](#example%201-5%20change%20a%20normal%20column%20to%20an%20auto%20increment%20column), [add a column](#example%201-6%20add%20a%20column), [delete a column](#example%201-7%20drop%20a%20column), [add a primary key](#example%201-8%20add%20a%20primary%20key), [modify a primary key](#example%201-9%20modify%20a%20primary%20key), [delete a primary key](#example%201-10%20drop%20a%20primary%20key), [add a foreign key](#example%201-11%20add%20a%20foreign%20key), [delete a foreign key](#example%201-12%20drop%20a%20foreign%20key), [add a CHECK constraint](#example%201-13%20add%20a%20check%20constraint), and [modify a table partition](#example%202-modify%20the%20partitioning%20rule%20of%20a%20table).
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
|
@ -487,4 +487,4 @@ CREATE TABLE table_name (column_name column_type[,column_name column_type])
|
|||
|
||||
## Subsequent operations
|
||||
|
||||
After creating a partition, you can add, drop, or truncate the partition. For information about partition management, see [Manage a partitioned table](../700.create-and-manage-partition-table/300.manage-level-1-partition-table.md).
|
||||
After creating a partition, you can add, drop, or truncate the partition. For information about partition management, see [Manage a partitioned table](3.manage-level-1-partition-table.md).
|
||||
|
|
@ -6,7 +6,7 @@ You can use the `CREATE INDEX` statement to create an index on a table.
|
|||
|
||||
OceanBase Database allows you to create an index on both partitioned and non-partitioned tables. An index can be either a local index or a global index. In addition, it can either be a unique index or a normal index. A local unique index on a partitioned table must include a partitioning key of the table.
|
||||
|
||||
This topic describes how to create an index on a non-partitioned table. For information about how to create an index on a partitioned table, see [Indexes on partitioned tables](../700.create-and-manage-partition-table/700.partition-table-index.md).
|
||||
This topic describes how to create an index on a non-partitioned table. For information about how to create an index on a partitioned table, see [Indexes on partitioned tables](../7.create-and-manage-partition-table/7.partition-table-index.md).
|
||||
|
||||
## Syntax
|
||||
|
||||
|
|
@ -31,6 +31,7 @@ table_definition:
|
|||
| [CONSTRAINT [constraint_name]] PRIMARY KEY index_desc
|
||||
| [CONSTRAINT [constraint_name]] UNIQUE {INDEX | KEY} [index_name] index_desc
|
||||
| {INDEX | KEY} [index_name] index_desc
|
||||
| FULLTEXT [INDEX | KEY] [index_name] fulltext_index_desc
|
||||
|
||||
column_definition_list:
|
||||
column_definition [, column_definition ...]
|
||||
|
|
@ -43,6 +44,9 @@ column_definition:
|
|||
index_desc:
|
||||
(column_desc_list) [index_type] [index_option_list]
|
||||
|
||||
fulltext_index_desc:
|
||||
(column_desc_list) CTXCAT(column_desc_list) [index_option_list]
|
||||
|
||||
column_desc_list:
|
||||
column_desc [, column_desc ...]
|
||||
|
||||
|
|
@ -209,6 +209,6 @@ obclient> SELECT LOWER(empname), sal, deptno FROM emp;
|
|||
6 rows in set
|
||||
```
|
||||
|
||||
In addition, you can use the `WHERE` clause to query specified columns. For more information, see [WHERE queries](../300.query/400.conditional-query.md).
|
||||
In addition, you can use the `WHERE` clause to query specified columns. For more information, see [WHERE queries](4.conditional-query.md).
|
||||
|
||||
For more information, see [Use operators and functions in queries](900.use-operators-and-functions-in-queries/100.use-arithmetic-operators-in-queries.md).
|
||||
For more information, see [Use operators and functions in queries](9.use-operators-and-functions-in-queries/1.use-arithmetic-operators-in-queries.md).
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue