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

  • Home
  • SEARCH
  • 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 8306353
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 8, 20262026-06-08T18:18:54+00:00 2026-06-08T18:18:54+00:00

Can I somehow force mysql to do a full scan on the subquery result

  • 0

Can I somehow force mysql to do a full scan on the subquery result instead of the existing table?

Let’s say I’ve got a query:

DELETE FROM table_a WHERE id IN (SELECT id FROM table_b WHERE ...)

If I’m sure that the subquery returns ~10 results, while table_a has thousands, can I somehow force table_a records to be looked up, and table_b result to be scanned? Mysql insists (according to EXPLAIN SELECT * FROM table_a...) to do ALL on table_a and index lookup on table_b.

  • 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-06-08T18:18:55+00:00Added an answer on June 8, 2026 at 6:18 pm

    Instead you can add index on field id and try INNER JOIN:

    DELETE a
    FROM table_a a 
         INNER JOIN table_b b
             ON a.id = b.id;
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Can I somehow force a derived class to always call the overridden methods base?
Can I somehow force execution order in my features and scenarios or in Nunit
In Java, can I somehow force a class that extends an abstract class to
Can I somehow disable ListView items navigation through keyboard (arrow keys), and leave navigation
Can you somehow lock an iPad to Safari and only one webpage? I've found
Can I somehow automatically add a node to a specific nodequeue when it is
Can anyone tell me, if in PostSharp, I somehow can turn on/off tracing in
I've been working all day and I somehow can't get this probably easy task
looper = (0..3).cycle 20.times { puts looper.next } can I somehow find the next
I would like to avoid the if statement below. Can I somehow copy the

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.