Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-6107

merge default_tmp_storage_engine

        Details

        • Type: Task
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Fix Version/s: 10.1.0
        • Component/s: None
        • Labels:
          None

          Description

          merge default_tmp_storage_engine from 5.6

            Gliffy Diagrams

              Attachments

                Issue Links

                relates to

                Bug - A problem which impairs or prevents the functions of the product. MDEV-8581 Unique prefix for default-tmp-storage-engine does not work

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Closed

                  Activity

                  Ascending order - Click to sort in descending order
                  Hide
                  Permalink
                  serg Sergei Golubchik added a comment -

                  Could you please review this? Thanks!

                  Show
                  serg Sergei Golubchik added a comment - Could you please review this? Thanks!
                  Hide
                  Permalink
                  bar Alexander Barkov added a comment -

                  The patch looks good. Okey to push.

                  Show
                  bar Alexander Barkov added a comment - The patch looks good. Okey to push.
                  Hide
                  Permalink
                  ccalender Chris Calender added a comment -

                  Could this be backported to MariaDB 10.0?

                  I know it would technically be introducing a change in behavior into a stable version, but this would actually make MariaDB 10.0 more compatible with MySQL 5.6, since this option exists in MySQL 5.6. I think the latter, in this specific case, outweighs the former.

                  Show
                  ccalender Chris Calender added a comment - Could this be backported to MariaDB 10.0? I know it would technically be introducing a change in behavior into a stable version, but this would actually make MariaDB 10.0 more compatible with MySQL 5.6, since this option exists in MySQL 5.6. I think the latter, in this specific case, outweighs the former.

                    People

                    • Assignee:
                      serg Sergei Golubchik
                      Reporter:
                      serg Sergei Golubchik
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      5 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved:

                        Time Tracking

                        Estimated:
                        Original Estimate - 1 day
                        1d
                        Remaining:
                        Time Spent - 5 hours Remaining Estimate - 3 hours
                        3h
                        Logged:
                        Time Spent - 5 hours Remaining Estimate - 3 hours
                        5h