Dathan Vance Pattishall wrote:One -->possibility would be to break the values out into multiple columns, one -->for each view, and have indexes on each of those columns, or at least -->the views that you consider most important. It might help to make them -->compound indexes, with each including several views that you think are -->likely to be searched on together.
Compound indexes do not work with the OR sql statement across different
True, but I believe you can get around that by doing UNIONs instead of ORs.columns. Doing the bitwise query essentially allows for the OR. If I'm wrong please some one let me know, I haven't seen it work yet.
Ah, I didn't realize that these weren't yes/no issues. If there are 32 possible answers for each of the questions, won't that prevent you from using the bitwise structure you described in any case?Also imagine using this approach on 16 different questions-politics, social background, religion, etc. This would be 16*32 columns such that 32 is the number of possible answers for each of the 16 questions.
-->However... aren't you worried that a 'politics' table is likely to be -->corrupt? <g>
Funny
Sorry -- I couldn't resist!
Bruce Feist
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
