Re: Calculated "virtual" rows
> Wouldn't the UNION ALL still be a performance bottleneck?
Think of UNION ALL as doing two separate SELECTs, then delivering their outputs together. Not a bottleneck.
UNION DISTINCT is, logically, UNION ALL plus dedupping the result. So it is more (perhaps not much more) effort.
I don't see anything that leads to column limitations. Do _not_ have separate columns for things like years, regions, etc. Those should be handled by separate _rows_. There is virtually no limit on the number of rows in a table.
> All other figures should ...
Please explain further. How many other figures? Will you use any of them in WHERE clauses? Could they be thrown into a single BLOB column of 'other stuff'? (I recommend JSON; XML is another possibility.)
Subject
Written By
Posted
Re: Calculated "virtual" rows
July 31, 2012 08:39PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.