Apache ShardingSphere v5.5.0 document
Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516 11.8 Pipeline E2E Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517 11.8 association will occur, affecting query efficiency. For example, if the t_order table and t_order_item table are both sharded according to order_id and are correlated using order_id, the two tables are SQL is: 8.1. Sharding 23 Apache ShardingSphere 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 relationships0 码力 | 602 页 | 3.85 MB | 1 年前3《Redis使用手册》(试读版)
并说明如何使⽤这些命令去构建各种实⽤的程序。 4.1 LPUSH:将元素推⼊到列表左端 ⽤户可以通过 LPUSH 命令, 将⼀个或多个元素推⼊到给定列表的左端: LPUSH list item [item item ...] 在推⼊操作执⾏完毕之后, LPUSH 命令会返回列表当前包含的元素数量作为返回值。 ⽐如以下代码就展示了如何通过 LPUSH 命令, 将 "buy some milk" 、 命令类似, 这两个命令执⾏的都是元素推⼊操作, 它们之间唯⼀的区别就在于 LPUSH 命令会 将元素推⼊列表左端, ⽽ RPUSH 命令则会将元素推⼊列表右端: RPUSH list item [item item ...] 在推⼊操作执⾏完毕之后, RPUSH 命令会返回列表当前包含的元素数量作为返回值。 举个例⼦, 以下代码展示了如何通过 RPUSH 命令, 将 "buy some milk" LPUSH list1 "item1" (integer) 1 redis> RPUSH list2 "item1" (integer) 1 图 4-9 两个只包含单个元素的列表 除了 LPUSH 命令和 RPUSH 命令之外, Redis 还提供了 LPUSHX 命令和 RPUSHX 命令: LPUSHX list item RPUSHX list item 这两个命令对待空列表的⽅式跟0 码力 | 352 页 | 6.57 MB | 1 年前3Apache ShardingSphere v5.5.0 中文文档
目标 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477 11.7 Pipeline E2E 测试 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478 11.7.1 卡尔积关联或跨库关联,从而影响查询效率。例如:t_order 表和 t_order_item 表,均按照 order_id 分片,并且使用 order_id 进行关联,则此两张表互为绑定表关系。绑定表之间的多表关联查询不会出 现笛卡尔积关联,关联查询效率将大大提升。举例说明,如果 SQL 为: SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id 条,它们呈现为笛卡尔积: SELECT i.* FROM t_order_0 o 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_id0 码力 | 557 页 | 4.61 MB | 1 年前3Apache ShardingSphere 5.4.1 Document
Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 11.8 Pipeline E2E Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 11.8 association will occur, affecting query efficiency. For example, if the t_order table and t_order_item table are both sharded according to order_id and are correlated using order_id, the two tables are SQL is: 8.1. Sharding 23 Apache ShardingSphere 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 relationships0 码力 | 572 页 | 3.73 MB | 1 年前3Apache ShardingSphere 中文文档 5.4.1
目标 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 11.7 Pipeline E2E 测试 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 11.7.1 卡尔积关联或跨库关联,从而影响查询效率。例如:t_order 表和 t_order_item 表,均按照 order_id 分片,并且使用 order_id 进行关联,则此两张表互为绑定表关系。绑定表之间的多表关联查询不会出 现笛卡尔积关联,关联查询效率将大大提升。举例说明,如果 SQL 为: SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id 条,它们呈现为笛卡尔积: SELECT i.* FROM t_order_0 o 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_id0 码力 | 530 页 | 4.49 MB | 1 年前3Apache ShardingSphere 中文文档 5.3.2
目标 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430 11.7 Pipeline E2E 测试 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431 11.7.1 卡尔积关联或跨库关联,从而影响查询效率。例如:t_order 表和 t_order_item 表,均按照 order_id 分片,并且使用 order_id 进行关联,则此两张表互为绑定表关系。绑定表之间的多表关联查询不会出 现笛卡尔积关联,关联查询效率将大大提升。举例说明,如果 SQL 为: SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i.order_id 条,它们呈现为笛卡尔积: SELECT i.* FROM t_order_0 o 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_id0 码力 | 508 页 | 4.44 MB | 1 年前3PostgreSQL 14.10 Documentation
Asynchronous Command Processing ...................................................... 885 34.5. Pipeline Mode ................................................................................... 889 34 relational databases out there behave. (If your problem is a program crash, you can obviously omit this item.) • Any command line options and other start-up options, including any relevant environment variables one uses a new syntax. It is not attached to a particular column, instead it appears as a separate item in the comma-separated column list. Column definitions and these constraint definitions can be listed0 码力 | 2871 页 | 13.38 MB | 1 年前3PostgreSQL 14.10 Documentation
Asynchronous Command Processing ........................................................... 930 34.5. Pipeline Mode ......................................................................................... 934 relational databases out there behave. (If your problem is a program crash, you can obviously omit this item.) • Any command line options and other start-up options, including any relevant environment variables one uses a new syntax. It is not attached to a particular column, instead it appears as a separate item in the comma-separated column list. Column def- initions and these constraint definitions can be listed0 码力 | 3032 页 | 13.27 MB | 1 年前3PostgreSQL 15.5 Documentation
Asynchronous Command Processing ...................................................... 910 34.5. Pipeline Mode ................................................................................... 914 34 relational databases out there behave. (If your problem is a program crash, you can obviously omit this item.) • Any command line options and other start-up options, including any relevant environment variables one uses a new syntax. It is not attached to a particular column, instead it appears as a separate item in the comma-separated column list. Column definitions and these constraint definitions can be listed0 码力 | 2910 页 | 13.60 MB | 1 年前3PostgreSQL 15.5 Documentation
Asynchronous Command Processing ........................................................... 955 34.5. Pipeline Mode ......................................................................................... 959 relational databases out there behave. (If your problem is a program crash, you can obviously omit this item.) • Any command line options and other start-up options, including any relevant environment variables one uses a new syntax. It is not attached to a particular column, instead it appears as a separate item in the comma-separated column list. Column def- initions and these constraint definitions can be listed0 码力 | 3073 页 | 13.49 MB | 1 年前3
共 227 条
- 1
- 2
- 3
- 4
- 5
- 6
- 23