Re: Opinons/Philosophy on adding flags to table to reduce queries?

Hi Jeff,
If mentioned table _is_ static, have You thought about splitiing it into the 'true' and 'false' part,
putting a view '<true> union <false>' into DB as substitute for the original table?
I can't judge if it's practical, 'cause I don't know the application aroud.

Rolf "Full table scan isn't a 4letter word"

Jeff Wilson <jwilson2000_at_home.com> schrieb in im Newsbeitrag: Xgc07.288435$p33.5772965_at_news1.sttls1.wa.home.com...
> What is the conventional wisdom regarding adding a boolean column to a
 table
> that is simply the result of a test on the values in about 6 other
 columns?
>
> I'm dealing with large tables and my query currently involves conditions
 on
> the values of these 6 columns. I index all of these columns, but it seems
> like it would be much faster to simply look at a single boolean value.
> Probably about 80% of the rows in the table pass the boolean test.
>
> The data in this table is fixed so I don't have to worry about an update
> affecting theboolean.
>
> Would only a purist avoid something like this? Are there considerations
> here I'm missing?
>
> Thanks.
>
> --
> Jeff Wilson
> jwilson2000_at_home.com
> Eugene, Oregon
>
> (541) 684-8590
>
>
Received on Sat Jul 21 2001 - 16:18:36 CDT