Subject | Re: [firebird-support] performance on calculated fields - performance question |
---|---|
Author | Lester Caine |
Post date | 2015-04-29T20:53:09Z |
On 29/04/15 21:40, shg_sistemas@... [firebird-support] wrote:
created when a record is accessed. What would be better in your case is
to create the calculated field in a trigger and add it to the record.
That way the data can be indexed and searched like any other field.
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
> With 40.000 records, I have no problem with this. But do you think itThe calculated fields don't actually exist in the database. They are
> will be very bad as the customers keep growing?
>
> I mean, generally speaking, it's "expensive" (regarding to the speed) to
> have calculated fields??
created when a record is accessed. What would be better in your case is
to create the calculated field in a trigger and add it to the record.
That way the data can be indexed and searched like any other field.
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk