Re: Problems with SELECT *
Date: Fri, 14 Mar 2003 13:33:34 -0500
Message-ID: <0Kpca.45$gD4.5257306_at_mantis.golden.net>
"Pablo Sanchez" <pablo_at_dev.null> wrote in message
news:Xns933E66570C586pingottpingottbah_at_216.166.71.233...
> cimarron+google_at_taylors.org (Cimarron Taylor) wrote in
> news:29e28c51.0303131009.10514345_at_posting.google.com:
>
> > Not if the system is column-oriented or if the table uses
> > a "Vertical Partitioning" scheme.
>
> I've yet to see someone design a system where you have _one_ column
> per table and those tables are coalesced to produce the result set --
> imagine how poor the performance would be otherwise!
>
> When veritical partitioning is employed, it's usually to group like
> columns.
According to Dennis Shasha's and Philippe Bonnet's recent update, _Database Tuning: Principles, Experiments, and Troubleshooting Techniques_, to Shasha's earlier book, a product called kdb physically stores tables as arrays of the columns. Received on Fri Mar 14 2003 - 19:33:34 CET