| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> comp.databases.theory -> Re: All hail Neo!
Marshall Spight wrote:
> Frank Hamersley wrote:
>> I can cope with that - I would have no problem being forced to write >> >> "select avg(age) from table where age is not null" >> >> to get the crappy statistic that it is if the user demanded it.
I fully understand the sentiment however in cases like this I prefer arrangements that retain flexibility for the (awake) programmer and provide a form of simple clarity. i.e. if there is one null the avg() is null. It would not take long for the industry to adopt this although with all existing code out there a change might take on Y2K proportions!
This simplistic approach means any stray nulls creeping into a dataset where none are expected will not go undetected if inadequately constrained queries are framed. Of course this a very late stage to be worrying about data integrity but better late than never.
Of course this is a simple case which is why I am interested to see if Bob comes up with insights into something more difficult.
Cheers, Frank. Received on Wed Apr 26 2006 - 08:12:46 CDT
![]() |
![]() |