First come into contact with Sharding - JDBC, paging question about Sharding - JDBC,

Some posts about Sharding - JDBC suggest using Sharding - JDBC, try to avoid using paging operation, because paging will bring more the amount of data query and result merging, and reduces the performance of the database,

If paging does not exist across the table query, such as a primary key positioning as a condition to the same table, if you won't be redundant query and merge the results?

If there is still a merge operation? On the premise of must use paging, whether there is a good optimization plan or strategy?

Aimed at the situation on the lot of the same problems: don't know what to optimize already exists in the latest Sharding - JDBC?

https://github.com/dangdangdotcom/sharding-jdbc/issues/79

Thanks in advance.

CodePudding user response:

Is to ask the landlord to solve the ~