Timeline for Storing a large number of small size entries in MySQL
Current License: CC BY-SA 2.5
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 31, 2011 at 1:54 | comment | added | Patrick | partitioning looks very interesting, I'm going to have to research how well I can implement this in symfony | |
| Jan 28, 2011 at 18:22 | comment | added | Joe | @Patrick : you might be able to use partitioning to avoid having to break them apart yourself, so long as you don't fall into any of the limitatons | |
| Jan 28, 2011 at 17:53 | vote | accept | Patrick | ||
| Jan 28, 2011 at 17:52 | comment | added | Patrick | I believe I will make the changes as you suggested and may, in the future, break out the data into different tables for each year to keep the tables from getting absolutely massive. Then I have to deal with getting symfony to understand that... other days - other problems | |
| Jan 28, 2011 at 16:37 | history | edited | Joe | CC BY-SA 2.5 |
added update
|
| Jan 28, 2011 at 16:00 | comment | added | Joe | It's not as pretty, but there are ways to work with RRD from PHP. | |
| Jan 28, 2011 at 15:41 | comment | added | Patrick | Those data analysis options look nice, however I'm in a PHP shop and am reluctant to have to branch to other languages just for graphing (none of the tools have a PHP API). I think that would introduce more room for bugs. | |
| Jan 27, 2011 at 15:35 | history | answered | Joe | CC BY-SA 2.5 |