SOMETHINGS C++ DOES RIGHT Patrice Roy Patrice.Roy@USherbrooke.ca; Patrice.Roy@clg.qc.ca CeFTI, Université de Sherbrooke; Collège Lionel-GroulxWho am I? • Father of five (four girls, one boy), ages However, there are a significant number of things C++ does right 11You might have heard… • However, there are a significant number of things C++ does right • There are a number of reasons why we love this this language... 12You might have heard… • However, there are a significant number of things C++ does right • There are a number of reasons why we love this language... • …love it so much that we gather

in --config?· · · · · · · · · · · · · · · 1205 7.7.10 Does TiCDC support outputting data changes in the Canal protocol? · 1205 7.7.11 Why does the latency from TiCDC to Kafka become higher and higher · · · · · · · · · · · · · · · · · · · · · · · · 1206 7.7.14 When TiCDC replicates data to Kafka, does a message contain multiple types of data changes?· · · · · · · · · · · · · · · · · · · · · · · · · in a message? · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 1207 11 7.7.17 How does TiCDC Open Protocol represent null? · · · · · · · · · · · · · · · · · · 1207 7.7.18 How can I tell

· · · · · · · · · · · · · · · · 5229 15.3.1 Does TiDB support the secondary key? · · · · · · · · · · · · · · · · · · · · · · · · · · · 5229 15.3.2 How does TiDB perform when executing DDL operations on 5230 15.3.6 The order of results is different from MySQL when ORDER BY is omitted5230 22 15.3.7 Does TiDB support SELECT FOR UPDATE? · · · · · · · · · · · · · · · · · · · · · · · · · 5232 15.3.8 Can 15.3.9 What is the maximum number of statements in a transaction? · · · · · · · 5232 15.3.10 Why does the auto-increment ID of the later inserted data is smaller than that of the earlier inserted data

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Does the application need to know about the sharding scheme underneath Vitess? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Does the Primary Vindex for a tablet have to be the same as its Primary Key? . . . . . . . . . . . . . varbinary of arbitrary length can also be mapped as is to a keyspace id. This is what the binary vindex does. Resharding Vitess supports resharding, in which the number of shards is changed on a live cluster

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Does the application need to know about the sharding scheme underneath Vitess? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Does the Primary Vindex for a tablet have to be the same as its Primary Key? . . . . . . . . . . . . . cluster as a toposphere. Global Topology The global topology service stores Vitess-wide data that does not change frequently. Specifically, it contains data about keyspaces and shards as well as the master

any part of the PostgreSQL system. These terms should not be inter- preted too narrowly; this book does not have fixed presumptions about system administration procedures. xxxvi Preface 4. Further Information something or not, please report that too; it is a bug in the documentation. If it turns out that a program does something different from what the documentation says, that is a bug. That might include, but is not them from the screen) but all too often important details are left out because someone thought it does not matter or the report would be understood anyway. The following items should be contained in every

any part of the PostgreSQL system. These terms should not be interpreted too narrowly; this book does not have fixed presumptions about system administration procedures. 4. Further Information Besides something or not, please report that too; it is a bug in the documentation. If it turns out that a program does something different from what the documentation says, that is a bug. That might include, but is not them from the screen) but all too often important details are left out because someone thought it does not matter or the report would be understood anyway. The following items should be contained in every

· · · · · · · · · · · · · · · · 4877 15.3.1 Does TiDB support the secondary key? · · · · · · · · · · · · · · · · · · · · · · · · · · · 4877 15.3.2 How does TiDB perform when executing DDL operations on · · 4878 15.3.6 The order of results is different from MySQL when ORDER BY is omitted4878 15.3.7 Does TiDB support SELECT FOR UPDATE? · · · · · · · · · · · · · · · · · · · · · · · · · 4880 15.3.8 Can 15.3.9 What is the maximum number of statements in a transaction? · · · · · · · 4880 15.3.10 Why does the auto-increment ID of the later inserted data is smaller than that of the earlier inserted data

· · · · · · · · · · · · · · · · 5177 15.3.1 Does TiDB support the secondary key? · · · · · · · · · · · · · · · · · · · · · · · · · · · 5177 15.3.2 How does TiDB perform when executing DDL operations on · · 5178 15.3.6 The order of results is different from MySQL when ORDER BY is omitted5178 15.3.7 Does TiDB support SELECT FOR UPDATE? · · · · · · · · · · · · · · · · · · · · · · · · · 5180 15.3.8 Can 15.3.9 What is the maximum number of statements in a transaction? · · · · · · · 5180 15.3.10 Why does the auto-increment ID of the later inserted data is smaller than that of the earlier inserted data

· · · · · · · · · · · · · · · · 4804 15.3.1 Does TiDB support the secondary key? · · · · · · · · · · · · · · · · · · · · · · · · · · · 4804 15.3.2 How does TiDB perform when executing DDL operations on · · 4806 15.3.6 The order of results is different from MySQL when ORDER BY is omitted4806 15.3.7 Does TiDB support SELECT FOR UPDATE? · · · · · · · · · · · · · · · · · · · · · · · · · 4807 15.3.8 Can 15.3.9 What is the maximum number of statements in a transaction? · · · · · · · 4808 15.3.10 Why does the auto-increment ID of the later inserted data is smaller than that of the earlier inserted data