> > So, having _both_ is the best thing.
>
> Absolutely, that's always what I meant -- we already have views and views
> can do this type of stuff at SELECT time can't they? So it's not a change,
> just an addition
And the precalculated and stored on disk thing can be done with triggers.
A
> I guess it depends on what you're using it for -- disk space
> is cheap and
> abundant anymore, I can see some advantages of having it
> computed only once
> rather than X times, where X is the number of SELECTs as that
> could get
> costly on really high traffic servers.. Costly not so much
> > This is a summary of replies.
> >
> > 1. Calculated fields in table definitions . eg.
> >
> > Create table test (
> > A Integer,
> > B integer,
> > the_sum As (A+B),
> > );
> >
> > This functionality can be achieved through the use of views.
>
At 12:28 PM 11/23/00 +0100, Zeugswetter Andreas SB wrote:
>
>> Reason: I want to know if any of these features are scheduled.
>>
>> 1. Calculated fields in table definitions . eg.
>>
>>Create table test (
>> A Integer,
>> B integer,
>>the_sum As (A+B),
> Reason: I want to know if any of these features are scheduled.
>
> 1. Calculated fields in table definitions . eg.
>
>Create table test (
> A Integer,
> B integer,
>the_sum As (A+B),
> );
This is currently easily done with a procedure that takes a t
