Archives of the TeradataForum
Message Posted: Wed, 06 Apr 2005 @ 18:42:01 GMT
I have seen that in Cognos when we try to apply a "filter" to outer joined objects. The tables may be related in the tool via an outer join, but then Cognos would translate "filters" applied at runtime as only a WHERE clause and not an additional ON clause, as in your Desired SQL. I don't know if Cognos ever agreed it was a bug, but we assigned it as such, and created a work around by either never applying "filters" to outer joined objects or, most likely, by creating views in the DB that masked the outer join from the reporting tool. Cognos would then only look at this view and no longer have to generate outer join SQL.
For us, it had nothing to do with Teradata, its ODBC driver, CLI, or anything on the DB side. It was simply the way Cognos interpreted filters and generated SQL. I have not encountered that with any of the tools you mentioned, so I can't say if this is applicable to your situation :-(
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|