MySQL shouldn't "guess" at the variable names
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL Server |
Unknown
|
Unknown
|
||||
OurDelta |
New
|
Undecided
|
Unassigned | |||
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.1 |
Won't Fix
|
Undecided
|
Unassigned | |||
5.5 |
Won't Fix
|
Undecided
|
Unassigned | |||
5.6 |
Won't Fix
|
Low
|
Unassigned | |||
5.7 |
Fix Released
|
Low
|
Unassigned | |||
Percona patches |
Won't Fix
|
Undecided
|
Unassigned |
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://
Anyway, here's the bug. group_concat_
Version: '5.1.33-
090504 8:26:59 [Warning] option 'group_
[pythian@db02 avail_mysql]$ grep concat /etc/my.cnf
group_concat_
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-
and
5.0.67-
tags: | added: upstream |
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 concat_ max_len= mysql".
recognised by their shortest non-ambiguous versions. "group=mysql" is actually
seen as "group_
---------------
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)