Re: use index on a view

[lau ch]

Hi, Rick James, thanks for your priceless suggestion. I will recofigure the mysql and re-conduct my test. looks like a long road to go for manipulating such huge records(in terms of hundreds GB records)

In addition, can you clarify me if mysql is able to perform query the desired records from every underlying table from a view with "union all" tables first and then merge them into a signle record set and return. For example, does my understanding below is true?

I have tried the "explain select * from vw_all_tables where ind_column = 123456" for all blank underlying tables, the key index column also return NULL. This circumstance is bad. When query from a view with simply "union all" tables, I expect mysql will base on the where condition to find out all desired records for each table first and then merge them into a big record set and then return. (which the way the MSSQL behaves, as it can be check from MSSQL’s execution plan)
For example, I expect mysql will based on "ind_column = 123456" to query tbl01 and get the desired records for tbl01, say, 3000 records; then mysql will based on "ind_column = 123456" to query tbl02 and get, say 3045 records, from tbl02; and so on. Finally, mysql merges all these 3000 records, 3045 records, ..., into one result set and returns to client.