Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Will it not severely affect tjhe performance?
Or is there a better way to accomplish the same?
Thanx in advance…
EDIT
its related to a table that stores around 70 fields for a car, and i have to match requirement of a user to the availability of the car
and performance relative to “if there is any better way”
From the comments on the question:
With that structure, then I don’t see a reasonable alternative to using a bunch of
ANDoperators. You could shard the table on major criteria and then only query the relevant table, but that denormalizes it — with all the unpleasantness (difficulty with reports, modifications, maintenance) that implies.Until/unless you see a real performance problem, I wouldn’t worry about it. If/when you do, you’ll have data to use to compare other approaches.