• Sergey Petrunya's avatar
    Switching [EXPLAIN] UPDATE/DELETE to rely on query plan footprints. · ab4a13b2
    Sergey Petrunya authored
    This requires that subselect's footprints are saved before it is deleted.
    
    Attempt to save select's QPF exposes one to a variety of edge cases:
    - the select may be a UNION's "fake select" which has no valid id
    - optimization may fail in the middle (but subsequent JOIN::optimize() calls
      will succeed, despite the fact that there never was a query plan)
    ab4a13b2
sql_select.h 64.6 KB