Re: Theory of Timeseries extensions to SQL and database
Date: 27 Oct 2002 10:01:35 -0800
Message-ID: <c0d87ec0.0210271001.2dcc1f8e_at_posting.google.com>
>> I'm guessing here, but I assume what you mean here is that you
have a separate table for the domain and then in the original table
you only store a pointer or some identifier that points to the actual
domain value. <<
The real trick in Nucleus is that they compress the sparse matrix in
such a way that they can query it in its compressed form. The fact
that 'red' is the color of car "#12" in race (7) becomes one bit in a
compressed 3D bit space.
In effect, all columns are indexed.
This leads to some strange designs -- instead of storing a phone number (US format) as a single column, you store the parts separately (area code, exchange, phone number) and the physical data actually gets smaller.
Since you are looking at dimensions, you can ask questions like "What things in all the tables of the schema are red?" by rotations.
Click over and get their white papers for more details. Received on Sun Oct 27 2002 - 19:01:35 CET