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

My criteria is the read/write speed tradeoff. If you're doing a lot of reading and little writing the additional overhead required for the write is justified by the payback you get from reduced SELECT times.

Since you are not writing to the table in question (and you don't have to worry
about distributed user applications being ignorant of your change) it looks like a
good idea.

Jeff Wilson <jwilson2000_at_home.com> wrote in message news: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:35 CDT