Now, when the user terminal opens the page, it sends the latitude and longitude to the server. Then the server queries the database. SQL is not very complex. But if the number of users comes up, MySQL will certainly be Alexander. There are sphtracing solutions, but there is a problem of index reconstruction. How can this problem be solved? Now, when the user terminal opens the page, it sends the latitude and longitude to the server. Then the server queries the database. SQL is not very complex. But if the number of users comes up, MySQL will certainly be Alexander. There are sphtracing solutions, but there is a problem of index reconstruction. How can this problem be solved?
Reply content:
Now, when the user terminal opens the page, it sends the latitude and longitude to the server. Then the server queries the database. SQL is not very complex. But if the number of users comes up, MySQL will certainly be Alexander. There are sphtracing solutions, but there is a problem of index reconstruction. How can this problem be solved?
Elasticsearch Solution
I don't know if I understand it.
It can be partitioned into two tables. Score by Operation degree. 1. Create a table. So when we look up the dimension, we can run the corresponding table to check the dimension of the dimension that uses the dimension. If there is a gap in the exam, you can check the region table where the region is located and then the corresponding region table.