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.
Using InnoDB in MySQL, I want to speed up selects by utilizing the clustered index better, thus including more frequently used columns in the primary key.
But some frequent columns used are allowed to be null (and some times are). Is there any way to include these in the clustered index (and allow them to be null)?
If not, are there some workarounds or is there some other way to do something similar?
Normalizing the table to exclude the nullable field would work in this case (as commented by Battle_707).