ourdelta-developers team mailing list archive

["Sheeri K. Cabral" <awfief@xxxxxxxxx>]

I believe this is actually MySQL's fault:

http://bugs.mysql.com/bug.php?id=45379

The response is:

are you sure this is a bug and not just a confusion.  options have always been
recognised by their shortest non-ambiguous versions.  "group=mysql" is actually
seen as "group_concat_max_len=mysql".

---------------

which is ridiculous -- if there's confusion, then by definition, it's
not "non-ambiguous".

(I'd appreciate it if folks could add a comment to
http://bugs.mysql.com/bug.php?id=45379)

** Bug watch added: MySQL Bug System #45379
   http://bugs.mysql.com/bug.php?id=45379

-- 
group_concat_max_len problem
https://bugs.launchpad.net/bugs/371752
You received this bug notification because you are a member of OurDelta-
developers, which is the registrant for OurDelta.

Status in OurDelta - Builds for MySQL: New
Status in Patches for MySQL by Percona: New

Bug description:
(reported by Sheeri K. Cabral )

I did not know how to file a bug report against a Percona build of MySQL (not xtradb, that has a launchpad page...).  If there could be a clear place on the Percona Labs page, or the documentation page at http://www.percona.com/docs/wiki/patches:start, that would be helpful.
Anyway, here's the bug.  group_concat_max_len for some reason isn't set properly, even when it's explicitly set in the /etc/my.cnf (the default is 1024, and we get these errors no matter what we set the group_concat_max_len value in /etc/my.cnf to):

Version: '5.1.33-percona-log'  socket: '/mysql/data/mysql.sock'  port: 3306  MySQL Community Server (GPL)
090504  8:26:59 [Warning] option 'group_concat_max_len': unsigned value 0 adjusted to 4

[pythian@db02 avail_mysql]$ grep concat /etc/my.cnf
group_concat_max_len=1024

Please let me know if you need any additional information, or if there's an actual bug tracker that I've missed....

We've also seen this in:
5.0.67-d7-ourdelta-sail44-log
and
5.0.67-percona-highperf-b10-log