Re: mysql_upgrade shows errors
On 14.02.2007 08:00 CE(S)T, Colin Charles wrote: The MySQL 5.0 release is available as a binary and is currently at 5.0.27. Grab it at: http://dev.mysql.com/downloads/mysql/5.0.html#downloads I read in the news some time ago that MySQL 5.0 is only going to be available as source version in the future, which it currently looks like. (Can't currently find that news.) But a more important fact is that the MySQL pre-built binary doesn't work correctly on my machine, anything that links to the mysqlclient crashes when using SSL. Since I build MySQL from source, that's gone. MySQL server is version 5.0.33, OS is Debian Linux 3.1, previous MySQL version was 5.0.17, installed from the binary release. Whats wrong with using the version via apt-get? Debian has very sensible packaging, and its currently at version 5.0.32 afaik Not quite... I can choose from 4.0.24 and 4.1.11a. While 4.0 seems to be unsupported by MySQL AB for a while. What do the above error messages mean? The upgrade script picked up on the fact that you had duplicate column names I cannot already have duplicate column names, relational tables don't allow that. But as you see, I already found out that the error messages are normal and don't mean a thing. -- Yves Goergen LonelyPixel [EMAIL PROTECTED] Visit my web laboratory at http://beta.unclassified.de -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql_upgrade shows errors
Yves Goergen wrote: On 14.02.2007 08:00 CE(S)T, Colin Charles wrote: The MySQL 5.0 release is available as a binary and is currently at 5.0.27. Grab it at: http://dev.mysql.com/downloads/mysql/5.0.html#downloads I read in the news some time ago that MySQL 5.0 is only going to be available as source version in the future, which it currently looks like. (Can't currently find that news.) But a more important fact is that the MySQL pre-built binary doesn't work correctly on my machine, anything that links to the mysqlclient crashes when using SSL. Since I build MySQL from source, that's gone. Yes, so the idea behind this is one release source only, one release source + binary, one release source only, one release source + binary. Frequency should be similar to previous releases, so currently, 5.0.27 is in binary, 5.0.33 is in source only, and 5.0.35 will have both binaries and sources Regarding the SSL bug, can you please file a bug at bugs.mysql.com? MySQL server is version 5.0.33, OS is Debian Linux 3.1, previous MySQL version was 5.0.17, installed from the binary release. Whats wrong with using the version via apt-get? Debian has very sensible packaging, and its currently at version 5.0.32 afaik Not quite... I can choose from 4.0.24 and 4.1.11a. While 4.0 seems to be unsupported by MySQL AB for a while. Thats true, we've dropped support for 4.0 since end-2006. I believe the roadmap does say 4.1 will be dropped in due time too -- Colin Charles, Community Engineer MySQL AB, Melbourne, Australia, www.mysql.com Mobile: +614 12 593 292 / Skype: colincharles Web: http://www.bytebot.net/blog/ MySQL Forge: http://forge.mysql.com/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql_upgrade shows errors
Yves Goergen wrote: Hello, I noticed that the current MySQL 5.0 release is not available as binary, so I downloaded the source and compiled it on my testing machine. Compilation went fine and I can connect to the new MySQL server version. But then I tried to run the mysql_upgrade script to fix possible issues and here's what it gave me: The MySQL 5.0 release is available as a binary and is currently at 5.0.27. Grab it at: http://dev.mysql.com/downloads/mysql/5.0.html#downloads ERROR 1060 (42S21) at line 22: Duplicate column name 'File_priv' @hadGrantPriv:=1 1 1 ERROR 1060 (42S21) at line 28: Duplicate column name 'Grant_priv' ERROR 1060 (42S21) at line 29: Duplicate column name 'Grant_priv' ERROR 1060 (42S21) at line 30: Duplicate column name 'Grant_priv' ERROR 1060 (42S21) at line 41: Duplicate column name 'ssl_type' ERROR 1061 (42000) at line 66: Duplicate key name 'Grantor' ERROR 1054 (42S22) at line 102: Unknown column 'Type' in 'columns_priv' ERROR 1060 (42S21) at line 124: Duplicate column name 'type' @hadShowDbPriv:=1 1 1 (and some more similar stuff) I tried it twice. At the first time, all other tables had an OK besides them, at the second time, those lines didn't show up anymore. MySQL server is version 5.0.33, OS is Debian Linux 3.1, previous MySQL version was 5.0.17, installed from the binary release. Whats wrong with using the version via apt-get? Debian has very sensible packaging, and its currently at version 5.0.32 afaik What do the above error messages mean? The upgrade script picked up on the fact that you had duplicate column names -- Colin Charles, Community Engineer MySQL AB, Melbourne, Australia, www.mysql.com Mobile: +614 12 593 292 / Skype: colincharles Web: http://www.bytebot.net/blog/ MySQL Forge: http://forge.mysql.com/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql_upgrade shows errors
On 10.02.2007 17:39 CE(S)T, Yves Goergen wrote: ERROR 1060 (42S21) at line 22: Duplicate column name 'File_priv' (and some more similar stuff) As I found out I already asked that on a previous upgrade. Other sources make me think that this is not an actual error but intended if the tables are already up-to-date. Maybe there should just be a note at the end of the script that tells that it has completed and that tose error messages can be ignored (as is the case for several build systems, e.g. PHP's). I believe this would save you from a lot of asking faces of those that aren't so much into MySQL. -- Yves Goergen LonelyPixel [EMAIL PROTECTED] Visit my web laboratory at http://beta.unclassified.de -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysql_upgrade shows errors
Hello, I noticed that the current MySQL 5.0 release is not available as binary, so I downloaded the source and compiled it on my testing machine. Compilation went fine and I can connect to the new MySQL server version. But then I tried to run the mysql_upgrade script to fix possible issues and here's what it gave me: ERROR 1060 (42S21) at line 22: Duplicate column name 'File_priv' @hadGrantPriv:=1 1 1 ERROR 1060 (42S21) at line 28: Duplicate column name 'Grant_priv' ERROR 1060 (42S21) at line 29: Duplicate column name 'Grant_priv' ERROR 1060 (42S21) at line 30: Duplicate column name 'Grant_priv' ERROR 1060 (42S21) at line 41: Duplicate column name 'ssl_type' ERROR 1061 (42000) at line 66: Duplicate key name 'Grantor' ERROR 1054 (42S22) at line 102: Unknown column 'Type' in 'columns_priv' ERROR 1060 (42S21) at line 124: Duplicate column name 'type' @hadShowDbPriv:=1 1 1 (and some more similar stuff) I tried it twice. At the first time, all other tables had an OK besides them, at the second time, those lines didn't show up anymore. MySQL server is version 5.0.33, OS is Debian Linux 3.1, previous MySQL version was 5.0.17, installed from the binary release. What do the above error messages mean? -- Yves Goergen LonelyPixel [EMAIL PROTECTED] Visit my web laboratory at http://beta.unclassified.de -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
