> Does anyone know if there is a document that
> explains the BEST way to deal with tables and views? What
> I mean is... is it better to create a view that is
> comprised of numerous other tables or views rather than
> projecting tables and then combining them in a table or
> final view that contains the final result?
I don't think there are any hard and fast rules, since a difference in the
underlying data could determine which is the preferred way to go.
My personal rules are to use views where ever possible, for the following
reasons:
1. No programming involved (after the initial view creation).
2. No database expansion.
3. No second copy of the data stored to possibly get out of date.
4. Let the engine do its job (high speed data retrieval and join
optimization).
That said, sometimes you need to create a new table. In that case, I always
use the super-powerful, multi-user safe TEMP table feature of R:Base.
--
Larry
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
