有可能有一个MySQL索引视图?Is it possible to have an indexed view in MySQL?
I found a posting on the MySQL forums from 2005, but nothing more recent than that. Based on that, it's not possible. But a lot can change in 3-4 years.
What I'm looking for is a way to have an index over a view but have the table that is viewed remain unindexed. Indexing hurts the writing process and this table is written to quite frequently (to the point where indexing slows everything to a crawl). However, this lack of an index makes my queries painfully slow.
I don't think MySQL supports materialized views which is what you would need, but it wouldn't help you in this situation anyway. Whether the index is on the view or on the underlying table, it would need to be written and updated at some point during an update of the underlying table, so it would still cause the write speed issues.
Your best bet would probably be to create summary tables that get updated periodically.
(原文：Thanks. I did some more searching on materialized views, and it looks like you are correct.)
Have you considered abstracting your transaction processing data from your analytical processing data so that they can both be specialized to meet their unique requirements?
The basic idea being that you have one version of the data that is regularly modified, this would be the transaction processing side and requires heavy normalization and light indexes so that write operations are fast. A second version of the data is structured for analytical processing and tends to be less normalized and more heavily indexed for fast reporting operations.
Data structured around analytical processing is generally built around the cube methodology of data warehousing, being composed of fact tables that represent the sides of the cube and dimension tables that represent the edges of the cube.
(原文：That's actually what I'm working on now. I think. I'm going to have a table that has the data that I need that's updated on a regular basis that is indexed for queries, so I only have to query the unindexed table once every [long unit of time] to update the indexed table with new data.)
Do you only want one indexed view? It's unlikely that writing to a table with only one index would be that disruptive. Is there no primary key?
If each record is large, you might improve performance by figuring out how to shorten it. Or shorten the length of the index you need.
If this is a write-only table (i.e. you don't need to do updates), it can be deadly in MySQL to start archiving it, or otherwise deleting records (and index keys), requiring the index to start filling (reusing) slots from deleted keys, rather than just appending new index values. Counterintuitive, but you're better off with a larger table in this case.
Flexviews supports materialized views in MySQL by tracking changes to underlying tables and updating the table which functions as a materialized view. This approach means that SQL supported by the view is a bit restricted (as the change logging routines have to figure out which tables it should track for changes), but as far as I know this is the closest you can get to materialized views in MySQL.
- MySQL—;马克1匹配的行MySQL — mark all but 1 matching row
- 什么你读过的最好的书或文章优化mysql服务器(linux)?(关闭)Whats the best book or article you have read on optimizing mysql servers (linux)? [closed]
- 发现差异在MySQL的两个表的行数Finding difference in row count of two tables in MySQL
- 如何设置连接超时根据MySQL用户登录的吗How to setup a connection timeout depending of the user login in MySQL
- MySQL计数(不同的())意想不到的结果MySQL COUNT(DISTINCT()) unexpected results
- 有可能有一个MySQL索引视图?Is it possible to have an indexed view in MySQL?
- 什么是适当的交叉表的SQL查询语法吗?What is the proper syntax for a cross-table SQL query?
- 在MySQL中变量限制条款Variable LIMIT Clause in MySQL
- 从MySQL在Java中检索记录Retrieving records from MySQL in Java
- mysql导入脚本mysql import script
- 有什么问题这个create table语句(复制)What is wrong with this create table statement [duplicate]