Re: Wow - has anyone used ROW_NUMBER() to get around using a UNION statement when UNION ALL doesn't work??

The issue at hand here (people asking for more information) has nothing to do with a solving problem -- it has to do with having the right information to understand the full context of what your are discussing. Your question (below) requires more information for one to really offer any meaningful comments (not guessing). Specifically it requires seeing the full execution plan for all scenarios and the optimizer's estimated and actual row counts.

PS. if you dont want to post plans, etc on the list, I'd suggest making an account over at http://pastebin.com - that works quite well (and even uses a fixed width font).

On Sat, Aug 6, 2011 at 5:17 AM, Taylor, Chris David <ChrisDavid.Taylor_at_ingrambarge.com> wrote:
> Again, I'm not trying to solve a problem.  I'm curious if anyone has used row_number to get around using an UNION (when a UNION ALL is not an acceptable replacement).  And correlated to that if anyone wanted to discuss the pros and cons.

--
Regards,
Greg Rahn
http://structureddata.org
--
http://www.freelists.org/webpage/oracle-l