MySQL 客户 端连接。如果现有的业务已经基于 MySQL 开发，大多数情况不需要修改代码即可直接替换单机的 MySQL。 包括现有的大多数 MySQL 运维工具（如 PHPMyAdmin, Navicat, MySQL Workbench 等），以及备份恢复工 具（如 mysqldump, mydumper/myloader）等都可以直接使用。 不过一些特性由于在分布式环境下没法很好的实现，目前暂时不支持或者是表现与 本文档使用 书栈(BookStack.CN) 构建 支持更多 MySQL 语法 支持配置文件修改 lower_case_table_names 系统变量，用于支持 OGG 数据同步工具 提升对 Navicat 的兼容性 在 Information_Schema 中支持显示建表时间 修复部分函数/表达式返回类型和 MySQL 不同的问题 提升对 JDBC 兼容性 支持更多的 SQL_MODE DDL 操作变更为低优先级，降低对线上业务影响 支持参数为 JSON 类型的 SUM/AVG 等聚合函数 支持配置文件修改 lower_case_table_names 系统变量，用于支持 OGG 数据同步工具 提升对 Navicat 管理工具的兼容性 支持在 CRUD 操作中使用隐式的行 ID 支持 Region Merge，合并数据删除后产生的空 Region 或小 Region 添加副本时忽略有大量 pending peer

provide schemaMetaStructSQLite u Written for SQLite, but could support others u No macros u No code generatorsCreate Customers sqlite3 *sqldb; sqlite3_open(":memory:", &sqldb); ftsd::prepared_statement< bind_parameters(sqlite3_stmt *stmt, ParametersMetaStruct parameters) { int index = 1; meta_struct_for_each( [&](auto &m) mutable { auto r = bind_impl(stmt, index, m.value); check_sqlite_return(r parameters); }Reading SQL rows template auto read_row(sqlite3_stmt *stmt) { RowType row = {}; std::size_t count = sqlite3_column_count(stmt); auto size = meta_struct_size(row); assert(size

.unlock = pthread_mutex_unlock, .getsize = sqlite_usable_size, .nextitem = sqlite_pagecache_next, … }; #endifSimple SQL Database void sqlite_unlock(lock* l) { global_config.unlock(l); } pthread_mutex_unlockSimple SQL Database void sqlite_unlock(lock* l) { global_config.unlock(l); } void sqlite_getsize(void* p) { global_config.getsize(p); } void sqlite_nextitem(item* i) { global_config OpUmizaUons Benchmark Speedup Diff Size Change Summary memcached 9.39% -6, +2 removed unnecessary locks sqlite 25.60% -3, +3 removed DIY vtable implementa?on blackscholes 2.56% -61, +4 manual common subexpression

part of the file to reflect your database deployement. If you just want to try out things locally, sqlite3 is the easiest database to set up, however it should not be used in production. If you still wish should look like: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': os.path.join(PROJECT_DIR, 'database.sqlite'), } } URL configuration You need to include the ’cms.urls’ urlpatterns

part of the file to reflect your database deployement. If you just want to try out things locally, sqlite3 is the easiest database to set up, however it should not be used in production. If you still wish DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': os.path.join(PROJECT_DIR, 'database.sqlite'), } } 2.1.2. URL configuration You need to include the 'cms

suggestions differ from the default, they’re highlighted below: • Database configuration (in URL format): sqlite://localhost/project.db • django CMS version: stable • Django version: 1.6 • Activate Django I18N part of the file to reflect your database deployment. If you just want to try out things locally, sqlite3 is the easiest database to set up, however it should not be used in production. If you still wish should look like: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': os.path.join(BASE_DIR, 'database.sqlite'), } } Given django CMS’s support for Django 1.6.x, Django 1.7 (or later)

part of the file to reflect your database deployment. If you just want to try out things locally, sqlite3 is the easiest database to set up, however it should not be used in production. If you still wish should look like: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': os.path.join(PROJECT_PATH, 'database.sqlite'), } } URL configuration You need to include the ’cms.urls’ urlpatterns

part of the file to reflect your database deployment. If you just want to try out things locally, sqlite3 is the easiest database to set up, however it should not be used in production. If you still wish should look like: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': os.path.join(PROJECT_PATH, 'database.sqlite'), } } URL configuration You need to include the ’cms.urls’ urlpatterns

part of the file to reflect your database deployment. If you just want to try out things locally, sqlite3 is the easiest database to set up, however it should not be used in production. If you still wish should look like: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': os.path.join(PROJECT_PATH, 'database.sqlite'), } } URL configuration You need to include the ’cms.urls’ urlpatterns

part of the file to reflect your database deployment. If you just want to try out things locally, sqlite3 is the easiest database to set up, however it should not be used in production. If you still wish DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': os.path.join(PROJECT_PATH, 'database.sqlite'), } } 1.2.2. URL configuration You need to include the 'cms