Comentários (4)

1 dav1mo comentou às Link permanente

Somethimg is wrong with the font on this blog entry. It keeps getting larger and larger. To the point that it is no longer readable. Otherwise, I really enjoy some of the SQL tips you give.
Dave

2 SergeRielau comentou às Link permanente

Dave,

 
Thanks for letting me know. I have cleaned up the HTML. Hopefully that helped.

3 sayap comentou às Link permanente

Hi Serge,

 
Thanks for the article. It helps me solve my problem at http://stackoverflow.com/questions/7120427/db2-loses-track-of-table-after-getting-3-levels-deep-into-a-subquery/
 
Anyway, is there any plan to fix this:
 
> But DB2 also didn't jump two levels up to S.c1. I suppose it could but, alas, it does not.
 
Using LATERAL for this query doesn't look right, since the data is from outer-outer table, not sibling table.

4 SergeRielau comentou às Link permanente

Sayap,

 
I have seen what you describe sporadically. But since it happens very rarely and LATERAL fixes the problem there has been no problem to lift this restriction.
So, unless a customer raises this as a PMR I do not see this one change any time soon.
 
Cheers
Serge