Changes between Initial Version and Version 1 of Ticket #36213, comment 8


Ignore:
Timestamp:
Feb 26, 2025, 9:02:39 PM (5 days ago)
Author:
Simon Charette

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #36213, comment 8

    initial v1  
    77Not sure if this changes the outcome of this ticket but [https://github.com/django/django/compare/main...charettes:django:mysql-update-tweaks the first two commits of this branch seem to address the issue entirely] by
    88
    9 1. Materializing the subquery on the server side under all circumstances
     91. In cases where the subquer must be materialized favor doing so on the server side (same strategy as #31965).
    10102. In cases where the `UPDATE FROM` syntax can be used with `JOIN`s to avoid the materialization of a subquery (which MySQL is notably bad at) adopt a similar strategy to #23576 (7acef095d73322f45dcceb99afa1a4e50b520479). That's possible when no aggregation or related updates are used.
    1111
Back to Top