 |
|
| Computers Forum Index » Computer - Databases » Store derived data or use view?... |
|
Page 1 of 1 |
|
| Author |
Message |
| zaphod... |
 Posted: Fri Jul 03, 2009 9:03 pm |
|
|
|
Guest
|
I have a table which stores the absolute longitude of planetary position, eg:
MERCURY
---------------
157.65
SATURN
-------------
247.65
When 2 planets are a certain distance apart there is an 'aspect', eg. 90 degrees is a "square" aspect
I wish to record these aspects for different user profiles and eventually do searches for users who have the same aspect(s). Would it be better, in terms of search speed/efficiency, to calculate and store the aspect data, eg. Mercury/Saturn square, or should I just store the longitude data and create a view with the calculated aspects? I anticipate a large dataset of users so efficiency is very important.
zaphod |
|
|
| Back to top |
|
|
|
| Jasen Betts... |
| Posted: Sat Jul 04, 2009 1:15 pm |
|
|
|
Guest
|
On 2009-07-03, zaphod <abc at (no spam) def.com> wrote:
Quote: I have a table which stores the absolute longitude of planetary position, eg:
MERCURY
---------------
157.65
SATURN
-------------
247.65
When 2 planets are a certain distance apart there is an 'aspect', eg. 90 degrees is a "square" aspect
like astrology?
Quote: I wish to record these aspects for different user profiles and eventually do searches for users who have the same aspect(s). Would it be better, in terms of search speed/efficiency, to calculate and store the aspect data, eg. Mercury/Saturn square, or should I just store the longitude data and create a view with the calculated aspects? I anticipate a large dataset of users so efficiency is very important.
cpu is faster than disk just store time of birth, index on squareness etc. |
|
|
| Back to top |
|
|
|
|
|
All times are GMT
The time now is Wed Dec 02, 2009 4:39 am
|
|