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

GROUP_CONCAT not showing any output with group_concat_max_len >= 4Gb

        Details

        • Type: Bug
        • Status: Open
        • Priority: Minor
        • Resolution: Unresolved
        • Affects Version/s: 10.0.3, 5.5.31, 5.1.67, 5.2.14, 5.3.12
        • Fix Version/s: 10.0, 5.5
        • Component/s: None
        • Environment:
          Debian GNU/Linux 7.1 (wheezy)

          Description

          Every query using a GROUP_CONCAT is showing an empty resultset with no NULL values on the column it should concatenate.

          A simple "select studentId, group_concat(grades) from studentGrades where sutdentId=1" is giving a wrong output with the above description.

            Gliffy Diagrams

              Attachments

                Issue Links

                links to

                Web Link Bug #69515 - group_concat_max_len >= 4Gb does not work

                  Activity

                  Ascending order - Click to sort in descending order
                  5 older comments
                  Hide
                  Permalink
                  lweijl Lennart Weijl added a comment -

                  I wasn't aware that this value was set this high.

                  Maybe good to mention that I upgraded from MySQL 5.5.31+dfsg-0+wheezy1 to version 10.0.3 MariaDB. Before the update MySQL output of the query was the expected output, could this be causing the value from being set this high?

                  Either way, thanks a lot for the fast and good support!

                  Show
                  lweijl Lennart Weijl added a comment - I wasn't aware that this value was set this high. Maybe good to mention that I upgraded from MySQL 5.5.31+dfsg-0+wheezy1 to version 10.0.3 MariaDB. Before the update MySQL output of the query was the expected output, could this be causing the value from being set this high? Either way, thanks a lot for the fast and good support!
                  Hide
                  Permalink
                  elenst Elena Stepanova added a comment -

                  This is strange, the behavior on the server side seems to be like that in all versions down to at least 5.1, both MariaDB and MySQL.
                  It could however happen that the bad value somehow crept in with the upgrade or afterwards.
                  I'll check upgrade on Wheezy to make sure it doesn't come with the package. Meanwhile, can you check your config files and see where exactly the value is set? Also, are you the only one who has access to the files, can it be that somebody else modified it recently?

                  Show
                  elenst Elena Stepanova added a comment - This is strange, the behavior on the server side seems to be like that in all versions down to at least 5.1, both MariaDB and MySQL. It could however happen that the bad value somehow crept in with the upgrade or afterwards. I'll check upgrade on Wheezy to make sure it doesn't come with the package. Meanwhile, can you check your config files and see where exactly the value is set? Also, are you the only one who has access to the files, can it be that somebody else modified it recently?
                  Hide
                  Permalink
                  lweijl Lennart Weijl added a comment -

                  – Meanwhile, can you check your config files and see where exactly the value is set?
                  Will do and get back to you on that.

                  – Also, are you the only one who has access to the files, can it be that somebody else modified it recently?
                  Yes, I am the only one with access to this files/machine. I didn't modify them for at least a year ago, so no recent modifications on any config file. (Maybe the upgrade process did something on the config, will investigate that.)

                  Show
                  lweijl Lennart Weijl added a comment - – Meanwhile, can you check your config files and see where exactly the value is set? Will do and get back to you on that. – Also, are you the only one who has access to the files, can it be that somebody else modified it recently? Yes, I am the only one with access to this files/machine. I didn't modify them for at least a year ago, so no recent modifications on any config file. (Maybe the upgrade process did something on the config, will investigate that.)
                  Hide
                  Permalink
                  elenst Elena Stepanova added a comment -

                  Also refiled at MySQL bug base as http://bugs.mysql.com/bug.php?id=69515

                  Show
                  elenst Elena Stepanova added a comment - Also refiled at MySQL bug base as http://bugs.mysql.com/bug.php?id=69515
                  Hide
                  Permalink
                  lweijl Lennart Weijl added a comment -

                  Must have made a mistake (one * 1024 too many) a while ago since I set that value into the config myself. No error from the upgrade progress there but a human error.

                  Still a bug though, so I'm sort of glad we've run into this.

                  Thanks again! Set the value to a more acceptable amount and all is working again.

                  Show
                  lweijl Lennart Weijl added a comment - Must have made a mistake (one * 1024 too many) a while ago since I set that value into the config myself. No error from the upgrade progress there but a human error. Still a bug though, so I'm sort of glad we've run into this. Thanks again! Set the value to a more acceptable amount and all is working again.

                    People

                    • Assignee:
                      Unassigned
                      Reporter:
                      lweijl Lennart Weijl
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      3 Start watching this issue

                      Dates

                      • Created:
                        Updated: