MySQL Temporary tables currently hard code memory Storage Engine

Created on 17 January 2015, over 9 years ago
Updated 30 January 2023, over 1 year ago

Currently the MySQL temporary table code explicitly specifies that the storage engine should be MEMORY. While this may commonly be the case, there are some reasons to use other storage engines instead (for example: TEXT/BLOB support; more efficient usage by providing true variable length storage).

From MySQL 5.6, it is also possible to change what temporary tables are created as:
http://dev.mysql.com/doc/refman/5.6/en/server-system-variables.html#sysv...

πŸ“Œ Task
Status

Needs work

Version

10.1 ✨

Component
MySQL driverΒ  β†’

Last updated 23 days ago

Created by

πŸ‡¨πŸ‡¦Canada morgantocker

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • The Needs Review Queue Bot β†’ tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

    Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

    Consult the Drupal Contributor Guide β†’ to find step-by-step guides for working with issues.

Production build 0.69.0 2024