积分充值
 首页
前端开发
AngularDartElectronFlutterHTML/CSSJavaScriptReactSvelteTypeScriptVue.js构建工具
后端开发
.NetC#C++C语言DenoffmpegGoIdrisJavaJuliaKotlinLeanMakefilenimNode.jsPascalPHPPythonRISC-VRubyRustSwiftUML其它语言区块链开发测试微服务敏捷开发架构设计汇编语言
数据库
Apache DorisApache HBaseCassandraClickHouseFirebirdGreenplumMongoDBMySQLPieCloudDBPostgreSQLRedisSQLSQLiteTiDBVitess数据库中间件数据库工具数据库设计
系统运维
AndroidDevOpshttpdJenkinsLinuxPrometheusTraefikZabbix存储网络与安全
云计算&大数据
Apache APISIXApache FlinkApache KarafApache KyuubiApache OzonedaprDockerHadoopHarborIstioKubernetesOpenShiftPandasrancherRocketMQServerlessService MeshVirtualBoxVMWare云原生CNCF机器学习边缘计算
综合其他
BlenderGIMPKiCadKritaWeblate产品与服务人工智能亿图数据可视化版本控制笔试面试
文库资料
前端
AngularAnt DesignBabelBootstrapChart.jsCSS3EchartsElectronHighchartsHTML/CSSHTML5JavaScriptJerryScriptJestReactSassTypeScriptVue前端工具小程序
后端
.NETApacheC/C++C#CMakeCrystalDartDenoDjangoDubboErlangFastifyFlaskGinGoGoFrameGuzzleIrisJavaJuliaLispLLVMLuaMatplotlibMicronautnimNode.jsPerlPHPPythonQtRPCRubyRustR语言ScalaShellVlangwasmYewZephirZig算法
移动端
AndroidAPP工具FlutterFramework7HarmonyHippyIoniciOSkotlinNativeObject-CPWAReactSwiftuni-appWeex
数据库
ApacheArangoDBCassandraClickHouseCouchDBCrateDBDB2DocumentDBDorisDragonflyDBEdgeDBetcdFirebirdGaussDBGraphGreenPlumHStreamDBHugeGraphimmudbIndexedDBInfluxDBIoTDBKey-ValueKitDBLevelDBM3DBMatrixOneMilvusMongoDBMySQLNavicatNebulaNewSQLNoSQLOceanBaseOpenTSDBOracleOrientDBPostgreSQLPrestoDBQuestDBRedisRocksDBSequoiaDBServerSkytableSQLSQLiteTiDBTiKVTimescaleDBYugabyteDB关系型数据库数据库数据库ORM数据库中间件数据库工具时序数据库
云计算&大数据
ActiveMQAerakiAgentAlluxioAntreaApacheApache APISIXAPISIXBFEBitBookKeeperChaosChoerodonCiliumCloudStackConsulDaprDataEaseDC/OSDockerDrillDruidElasticJobElasticSearchEnvoyErdaFlinkFluentGrafanaHadoopHarborHelmHudiInLongKafkaKnativeKongKubeCubeKubeEdgeKubeflowKubeOperatorKubernetesKubeSphereKubeVelaKumaKylinLibcloudLinkerdLonghornMeiliSearchMeshNacosNATSOKDOpenOpenEBSOpenKruiseOpenPitrixOpenSearchOpenStackOpenTracingOzonePaddlePaddlePolicyPulsarPyTorchRainbondRancherRediSearchScikit-learnServerlessShardingSphereShenYuSparkStormSupersetXuperChainZadig云原生CNCF人工智能区块链数据挖掘机器学习深度学习算法工程边缘计算
UI&美工&设计
BlenderKritaSketchUI设计
网络&系统&运维
AnsibleApacheAWKCeleryCephCI/CDCurveDevOpsGoCDHAProxyIstioJenkinsJumpServerLinuxMacNginxOpenRestyPrometheusServertraefikTrafficUnixWindowsZabbixZipkin安全防护系统内核网络运维监控
综合其它
文章资讯
 上传文档  发布文章  登录账户
IT文库
  • 综合
  • 文档
  • 文章

无数据

分类

全部数据库(26)数据库中间件(26)

语言

全部中文(简体)(15)英语(9)

格式

全部PDF文档 PDF(26)
 
本次搜索耗时 0.126 秒,为您找到相关结果约 26 个.
  • 全部
  • 数据库
  • 数据库中间件
  • 全部
  • 中文(简体)
  • 英语
  • 全部
  • PDF文档 PDF
  • 默认排序
  • 最新排序
  • 页数排序
  • 大小排序
  • 全部时间
  • 最近一天
  • 最近一周
  • 最近一个月
  • 最近三个月
  • 最近半年
  • 最近一年
  • pdf文档 Apache ShardingSphere 5.1.1 Document

    applications and databases that use Database Mesh to visit databases will form a large grid system, where they just need to be put into the right positions accordingly. They are all governed by the mesh one for example, if SQL is: SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); When binding table relations are not configured, suppose the sharding key JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_0 o JOIN t_order_item_1 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_1
    0 码力 | 458 页 | 3.43 MB | 1 年前
    3
  • pdf文档 Apache ShardingSphere 5.4.1 Document

    same database can effectively avoid the trouble caused by distributed transactions. In scenarios where cross‐library transactions cannot be avoided, some businesses might still be in the need to maintain document SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); In the case where no binding table relationships are being set, assume that the sharding key JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_0 o JOIN t_order_item_1 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_1
    0 码力 | 572 页 | 3.73 MB | 1 年前
    3
  • pdf文档 Apache ShardingSphere 5.2.0 Document

    same database can effectively avoid the trouble caused by distributed transactions. In scenarios where cross‐library transactions cannot be avoided, some businesses might still be in the need to maintain 2.0 SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); In the case where no binding table relationships are being set, assume that the sharding key JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_0 o JOIN t_order_item_1 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_1
    0 码力 | 483 页 | 4.27 MB | 1 年前
    3
  • pdf文档 Apache ShardingSphere 5.0.0-alpha Document

    application and database that use Database Mesh to visit database will form a large grid system, where they just need to be put into the right position accordingly. They are all gov‐ erned by the mesh one for example, if SQL is: SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); When binding table relations are not configured, suppose the sharding key JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_0 o JOIN t_order_item_1 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_1
    0 码力 | 311 页 | 2.09 MB | 1 年前
    3
  • pdf文档 Apache ShardingSphere 5.1.2 Document

    applications and databases that use Database Mesh to visit databases will form a large grid system, where they just need to be put into the right positions accordingly. They are all governed by the mesh one for example, if SQL is: SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); When binding table relations are not configured, suppose the sharding key JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_0 o JOIN t_order_item_1 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_1
    0 码力 | 503 页 | 3.66 MB | 1 年前
    3
  • pdf文档 Apache ShardingSphere 中文文档 5.1.1

    现笛卡尔积关联,关联查询效率将大大提升。举例说明,如果 SQL 为: SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); 在不配置绑定表关系时,假设分片键 order_id 将数值 10 路由至第 0 片,将数值 11 路由至第 1 片,那 么路由后的 SQL JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_0 o JOIN t_order_item_1 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); 4.3. 数据分片 27 Apache JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_1 o JOIN t_order_item_1 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); 在配置绑定表关系,并且使用 order_id
    0 码力 | 409 页 | 4.47 MB | 1 年前
    3
  • pdf文档 Apache ShardingSphere 中文文档 5.1.0

    现笛卡尔积关联,关联查询效率将大大提升。举例说明,如果 SQL 为: SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); 在不配置绑定表关系时,假设分片键 order_id 将数值 10 路由至第 0 片,将数值 11 路由至第 1 片,那 么路由后的 SQL JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_0 o JOIN t_order_item_1 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); 4.3. 数据分片 27 Apache JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_1 o JOIN t_order_item_1 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); 在配置绑定表关系,并且使用 order_id
    0 码力 | 406 页 | 4.40 MB | 1 年前
    3
  • pdf文档 Apache ShardingSphere v5.5.0 document

    same database can effectively avoid the trouble caused by distributed transactions. In scenarios where cross‐library transactions cannot be avoided, some businesses might still be in the need to maintain document SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); In the case where no binding table relationships are being set, assume that the sharding key JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_0 o JOIN t_order_item_1 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_1
    0 码力 | 602 页 | 3.85 MB | 1 年前
    3
  • pdf文档 Apache ShardingSphere 5.0.0 Document

    applications and databases that use Database Mesh to visit databases will form a large grid system, where they just need to be put into the right positions accordingly. They are all governed by the mesh one for example, if SQL is: SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); When binding table relations are not configured, suppose the sharding key order_id=i.order_id WHERE o. order_id in (10, 11); 4.2. Sharding 24 Apache ShardingSphere document, v5.0.0 SELECT i.* FROM t_order_0 o JOIN t_order_item_1 i ON o.order_id=i.order_id WHERE o. order_id in
    0 码力 | 403 页 | 3.15 MB | 1 年前
    3
  • pdf文档 Apache ShardingSphere 中文文档 5.1.2

    现笛卡尔积关联,关联查询效率将大大提升。举例说明,如果 SQL 为: SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); 在不配置绑定表关系时,假设分片键 order_id 将数值 10 路由至第 0 片,将数值 11 路由至第 1 片,那 么路由后的 SQL JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_0 o JOIN t_order_item_1 i ON o.order_id=i.order_id WHERE o. 4.3. 数据分片 27 Apache ShardingSphere document JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); SELECT i.* FROM t_order_1 o JOIN t_order_item_1 i ON o.order_id=i.order_id WHERE o. order_id in (10, 11); 在配置绑定表关系,并且使用 order_id
    0 码力 | 446 页 | 4.67 MB | 1 年前
    3
共 26 条
  • 1
  • 2
  • 3
前往
页
相关搜索词
ApacheShardingSphere5.1Document5.45.25.0alpha中文文档v5document
IT文库
关于我们 文库协议 联系我们 意见反馈 免责声明
本站文档数据由用户上传或本站整理自互联网,不以营利为目的,供所有人免费下载和学习使用。如侵犯您的权益,请联系我们进行删除。
IT文库 ©1024 - 2025 | 站点地图
Powered By MOREDOC AI v3.3.0-beta.70
  • 关注我们的公众号【刻舟求荐】,给您不一样的精彩
    关注我们的公众号【刻舟求荐】,给您不一样的精彩