# Ruby/MySQL/Rails timeseries QN

**URL:** <https://www.ruby-forum.com/t/ruby-mysql-rails-timeseries-qn/75473>\
**Category:** Ruby\
**Created:** [November 10, 2006, 5:09am UTC](https://www.ruby-forum.com/t/ruby-mysql-rails-timeseries-qn/75473 "2006-11-10T05:09:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![bodikp](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/e79b87/32.png) [@bodikp](https://www.ruby-forum.com/u/bodikp)\
**Post date:** [November 10, 2006, 5:09am UTC](https://www.ruby-forum.com/t/ruby-mysql-rails-timeseries-qn/75473/1 "2006-11-10T05:09:16Z")

</div>

I’m starting an application that will create, persist, query, and  
display timeseries. I’m wondering how to best store these timeseries  
so they can be queried via metadata. Each timeseries object could be  
seven or eight metadata attributes and an array of say 80000  
integers. There could be 10000 or more timeseries. The timeseries  
values will be appended but not modified in place. I’d like to use  
the ActiveRecord / Rails approach here and was wondering whether  
BLOBs attribute, a filesystem or a combination approach makes sense  
for marshalling the array of values to a compact format.
