Home > Back-end >  Sharding - whether JDBC table would result in a slow query
Sharding - whether JDBC table would result in a slow query

Time:04-20

A SQL in database to perform as long as the zero point for a few seconds, but in the program execution will spend seven or eight seconds (dao layer method execution time), is this table lead to this situation, or elsewhere in the program has a problem,

CodePudding user response:

When a query have to table fields? No words will all table scan

CodePudding user response:

Not in theory, only the SQL will be a lot of time on the client side the default paging parameters on the belt, rule out the possibility to say again first

CodePudding user response:

Is the problem, my table fields is a six figures, with the top two table, query when no specific table field values, and the table top two fields, so that we can achieve the single table to check

CodePudding user response:

reference 1st floor lin351550660 response:
query time have to table fields? No words will all table scan

Now I directly use ${} will table field behind the table, the query faster, but I don't know this is good

CodePudding user response:

refer to the second floor maradona1984 response:
not in theory, only the SQL will be a lot of time on the client side the default paging parameters on the belt, rule out the possibility to say again first

Is a question of 1/f, said

CodePudding user response:

reference 4 floor qq_40983892 response:
Quote: reference 1st floor lin351550660 response:
query time have to table fields? No words will all table scan

Now I directly with ${} will be behind the table, table fields query faster, but I don't know this is good

Fast is solved?
  • Related