Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

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.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6096677
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T12:57:20+00:00 2026-05-23T12:57:20+00:00

I have a simple query that looks like select id, name from mytable where

  • 0

I have a simple query that looks like

select id, name from mytable where age=28 order by name

the EXPLAIN output confuses me, I got

possible_keys : age
key : name

Does that mean mysql finally decided to use the index ‘name’ to fetch all the rows? Is the age index used or not? How many indexes are used in this query? If it’s the name index that mysql finnally chooses to use, what happened to the ‘age’ index?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T12:57:21+00:00Added an answer on May 23, 2026 at 12:57 pm

    Indeed, name is used and age is not. Best solution is to have a combined key on both age and name (in that order). That way, queries can make use of this index when sorting and filtering on both columns.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a query that looks like the following SELECT t1.Name, t2.ID, t2.name FROM
I have a simple query like this: select * from mytable where id >
I have a simple SQL 'Select' query, and I'd like to dump the results
I have a MySQL table that looks like this: Table: Designer id: integer name:
I am totally new to SQL . I have a simple select query similar
I have a table which looks like this: Name | Quantity | Unit -------+-------------+----------
Say I have a model that looks like: class StockRequest(models.Model): amount_requested = models.PositiveIntegerField(null=True) amount_approved
I have a struct that's used in my internet application, which looks like: struct
I have a very simple table and I can happily query it using LINQ
I have a URI here in which a simple document.cookie query through the console

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.