 |
 |
Archives of the TeradataForum
Message Posted: Mon, 12 May 2008 @ 19:42:07 GMT
Subj: | | Re: View with Default and Null values |
|
From: | | Dieter Noeth |
Srikanth Goli wrote:
| I am noticing an issue in Teradata, when I do a left join with a view and do a select based on a field in the view being null. This field
has a default value defined. | |
| My problem is why the last SQL does not return any rows. My hypothesis is that since the view has a default defined, it assumes this field
will have default value for all rows in the join, even though this is a left join and NOT ALL rows may have a match. Regardless, I think this is
not ideal. Can the members confirm if this is not an acceptable behavior or a bug? Any workarounds (short of not using defaults in the
view?) | |
AFAIK this is a known bug and has been fixe some time ago.
What's your Teradata version?
Dieter
| |