Bug #9919 | Comment field with FEDERATED needs to be greater than 60 chars | ||
---|---|---|---|
Submitted: | 14 Apr 2005 21:06 | Modified: | 13 May 2006 4:00 |
Reporter: | [ name withheld ] | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.0.3-beta-log | OS: | Linux (linux) |
Assigned to: | Bugs System | CPU Architecture: | Any |
[14 Apr 2005 21:06]
[ name withheld ]
[3 Jun 2005 17:45]
Patrick Galbraith
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.mysql.com/documentation/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php Additional info: Federated in 5.0 uses the comment field, which is a working prototype, and at this stage in 5.0's schedule, can't be changed. Federated in 5.1 will use a privilege system which won't even use the comment field, so with this new connection scheme, this problem of not being able to store a connection string that's long will be solved.
[19 Sep 2005 19:16]
Vahram Sukyas
This is something that I'd love to see fixed as well -- it's fairly difficult to fit the connection string within this 60 char limitation. This issue still exists with 5.0.12-beta.
[16 Dec 2005 19:13]
Eric Herman
When last I looked at this, the problem still existed with long strings, but I did not determine the exact longest length of a CONNECTION string.
[23 Feb 2006 2:33]
Brian Aker
This was fixed a long time ago....
[13 May 2006 0:40]
Patrick Galbraith
Brian says 4k
[13 May 2006 4:00]
Paul DuBois
Insufficient information to write changelog entry. Closing with no entry.