Re: calculated field
A basic rule of database design is to minimise redundancy. And, every time to store a calculated result, you run the risk of skew. So unless the calculation is costly enough to justify storing the result, it's most always preferable to put such calculations straight into your queries, either as a function, or as inline sql, or as a column in a View (indeed that's mainly what Views are for).
Subject
Views
Written By
Posted
2791
November 28, 2014 11:37AM
Re: calculated field
1790
November 28, 2014 12:40PM
1537
November 28, 2014 02:47PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.