Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
For a website I am developing, I am going to store user activity information (like Facebook) and HTTP requests to the server into a MySQL database.
I was going to use InnoDB as the storage engine, however, I briefly read about the Archive storage engine and this sounds like the way forward for information which is only Inserted or Selected and never Updated or Deleted.
Before I proceed, I would like to know the any pros and cons to help me make a decision whether to use it or not.
We are not currently using the Archive storage engine, but have done some research on it. One requirement of our application is that it stores lots of historical information for long periods of time. That data is never updated, but needs to be selected occasionally.
So … with that in mind:
PROs
Very small footprint. Uses zlib for data compression.
More efficient/quicker backups due to small data file size.
CONs
Does not allow column indexes. Selects require a full table scan.
Does not support spatial data.
—
It is likely that we will not use this storage engine due to the indexing limitations.