On 6/14/07, Mathew <[EMAIL PROTECTED]> wrote:
The purpose of getting the data in the first place is to allow my boss
to see that people are still not doing things they are supposed to. He
can then send out reminders so we can establish better habits. My plan
is to replace the null value with a description making it obvious that
the value had not been set instead of just leaving a big ugly blank spot.
Keep up with my goings on at http://theillien.blogspot.com
In that case you may want to either not use that field for the key to
the hash or use nvl (or its equivalent in your RDBMS) to replace the
null with a unique value (something like nvl(column, "not set " ||
rowid)). Also, if all you want to do is show your boss that people
are not doing their jobs you can simply run
select updated_by, last_updated, count(*)
from tablename
where field_that_should_not_be_null is null
group by updated_by, last_updated
order by last_updated, updated_by;
Or better yet, modify the schema to make that column not nullable
(which it should be if null is not a valid value).
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://learn.perl.org/
