Title: using stored procedures from pro*c
Okay
guys after feeling like a purist and that NULLS should not be stuffed with
values just because - because of course maybe slight performance
issue, also is it really the same meaning? and wanting easy way to
build in consistency to data without changing data - in building base
tables for warehouse ran into problem creating materialized view.
Guess what? I got zero-length errors if
try to decode to NULL for rows where values Great for derived fields - they
default to '0's say and everything else NULLS or you have to have a separate
update process to NULLS after object built which in the case of mater. views
like largely defeats the purpose.
In
my previous builds of dwarehouses I did end up using a default other than
NULLS for all columns but seems cumbersome.
Is
there a way in mat. view or CTAS I can decode to null value but avoid
zero-length error without writing a function? Is there a way to
specify column precision in CTAS explicitly and would that
work??
|
