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.
I have a table in my schema that has a unique constraint on two columns:
UNIQUE(Column1, Column2)
The SQlite documentation tells me that this creates a unique index on these columns. My question is, does that make an explicitly created index on one of the columns, say Column1, redundant?
Yes to your example, no to your question.
A compound index on 2 columns would make the additional index on the first one redundant. However, the index on the second column might still be useful.
But if each of the columns is by itself unique, it’s possible you don’t need a compound index. You might want to look into that.
Having too many indexes is not always an obvious problem. But wasting resources, especially for redundant purposes, is always bad.