Re: [pilot-db-list] Re: calculated field

[Fab <kr...@bi...>]

> > Relational Detabase systems usually don't have such a feature
> > (and I think I know why). The data is not regarded as sorted
> > in any useful way until it's queried with a specific sort
> > order.
> 	I agree.  The way I see inter-record calculations working is
> exactly like this.  First records are sorted, then the script is run.
> When these scripts are rerun is a big question we should think about.

	IMHO, it's a problem that can be solved in distinguishing the
database fields from the "presentation" fields. Calculated fields should
be calculated only with fields from the same record. Inter-records
calculations like agregates should be calculated each time they are
displayed on a view. Doing so, you can maintain the relational point
of vue. Ok, you migt say, but calculations will take a long time. That's
true, but I can't find another way to solve the dilemna.
	BTW, such a way could lead to imagine "presentation only" fields,
with results not stored in the database, wich would be very cool for the
database volume. For exemple, if you have to display the sum of two
fields, why always store the result ? Or we could display some values
in alternate units without storing the same values.

	Fab.