Re: Normalization and Derived Information
From: Laconic2 <laconic2_at_comcast.net>
Date: Fri, 24 Sep 2004 11:26:41 -0400
Message-ID: <d9-dnV510d1RocncRVn-qQ_at_comcast.com>
Date: Fri, 24 Sep 2004 11:26:41 -0400
Message-ID: <d9-dnV510d1RocncRVn-qQ_at_comcast.com>
> Since a view generator is a special case of a SELECT generator, my
thinking
> runs towards using materialized derived columns in tables, so that the
> selects are always pulling simple columns and never calculating on the
fly.
Yup, a SELECT generator. Cool!
Another question is WHEN to do the materializing: at store time, at
retrieval time, or some time in between.
The same question occurs in compilers. There are some compilers that are
smart enough (or dumb enough) to
evaluate sqrt(2) at compile time, and merely store the result in the object