Progress does not support a Full Outer Join is there a workaround?
15 June, 2011
Hi,
Progress does not support a Full Outer Join!
Is there anyway YellowFin can implement this within YellowFin ?
Thanks
Progress does not support a Full Outer Join!
Is there anyway YellowFin can implement this within YellowFin ?
Thanks
Hi,
The best way around this would be set up two data sources (both to the same database), you could then do it as an advanced sub query.
In this case it should allow a full outer join.
Note:
Using an Advanced sub-query (with two separate data sources) means that the join between the two queries is done by Yellowfin rather than by the database.
eg. The main query and the sub query are performed as two separate queries against the two data sources, then Yellowfin merges the data sets.
Because of this we can perform any type of join (even if the database doesn't support it natively). The downside is that it might be slower for Yellowfin to do the join than the database itself, especially with large result sets.
Other than that, there shouldn't be too much difference.
Regards,
David
The best way around this would be set up two data sources (both to the same database), you could then do it as an advanced sub query.
In this case it should allow a full outer join.
Note:
Using an Advanced sub-query (with two separate data sources) means that the join between the two queries is done by Yellowfin rather than by the database.
eg. The main query and the sub query are performed as two separate queries against the two data sources, then Yellowfin merges the data sets.
Because of this we can perform any type of join (even if the database doesn't support it natively). The downside is that it might be slower for Yellowfin to do the join than the database itself, especially with large result sets.
Other than that, there shouldn't be too much difference.
Regards,
David